This chapter describes APPN and includes the following sections:
Advanced Peer-to-Peer networking (APPN) extends the SNA architecture by enabling Type 2.1 (T2.1) nodes to communicate directly without requiring the services of a SNA host computer.
T2.1 nodes can activate connections with other T2.1 nodes and establish LU-LU sessions with other nodes. The relationship between a pair of T2.1 nodes is referred to as a peer relationship because either side can initiate communication.
Prior to APPN, a T2.1 node could communicate directly with another T2.1 node, but required the services of a centralized SNA host to locate its partner and any associated resources. All routes between the two nodes were predefined. APPN enhanced the T2.1 node function by:
The APPN architecture allows four types of nodes in a network:
The router can be configured as an APPN network node that supports connections with all four node types. The router cannot function as an end node for APPN.
An APPN network node provides directory and routing services for all resources (LUs) in its domain. A network node's domain consists of:
APPN network nodes also:
As a network node, the router can act as a server to attached APPN end nodes and LEN end nodes and provide functions that include:
An APPN end node provides limited directory, routing, and management services for logical units (LUs) associated with the node. An APPN end node selects a network node to be its network node server. If the network node agrees to act as the APPN end node's server, the end node can register its local resources with the network node. This enables the network node server to intercept and pass along search requests for resources located on the APPN end node.
The APPN end node and its network node server communicate by establishing CP-CP sessions. An APPN end node may be connected to a number of network nodes, but only one of these nodes acts as the APPN end node's server at any one time.
The APPN end node forwards all requests for unknown resources to the network node server. The network node server, in turn, uses its search facilities to locate the requested resource and calculate a route from the APPN end node to the resource.
A LEN node is a T2.1 node without APPN extensions. A LEN node can establish peer connections with other LEN nodes, APPN end nodes, and APPN network nodes, as long as all of the required destination LUs are registered with the LEN node. A LEN node can also serve as a gateway between an APPN network and a SNA subarea network.
Because a LEN node cannot establish CP-CP sessions with an APPN network node server, it cannot register its resources with the server or request that the server search for a resource and dynamically calculate a route to that resource. A LEN node may indirectly use the directory and routing services of a network node by pre-defining remote LUs (owned by nonadjacent nodes) as being located on an APPN network node, although the actual location may be anywhere in the network. When the LEN node needs to initiate a session with the remote LU, it sends a session activation request (BIND) for the LU to the network node. In this case, the network node acts as the LEN node's network node server, locating the requested resource, calculating a route, and forwarding the BIND to its correct destination.
When configuring the router network node, you can specify the names of LUs that are associated with an attached LEN end node. These LU names reside in the router network node's local directory. If the router network node receives a request to search for one of these LEN end node resources, it will be able to find the LU in its local directory and return a positive response to the node originating the search. To reduce the number of LU names you need to specify for an attached LEN end node, the router supports the use of generic LU names, which allow a wildcard character to represent a portion of an LU name.
A PU 2.0 node is a type T2.0 node containing dependent LUs. PU 2.0 nodes are supported by the Dependent LU Requestor (DLUR) function which is implemented by an APPN end node or network node. PU 2.0 nodes require the services of a system services control point, which is made available through the DLUR-enabled APPN node. Note that APPN nodes can contain dependent LUs supported by the DLUR function. However, the router does not contain dependent LUs.
The router implements the APPN Release 2 base architecture functions as defined in the Systems Network Architecture APPN Reference. The APPN network node functions implemented by the router are summarized in Table 1. Notes on specific functions follow the table. For a description of the APPN management services supported by the router, see "Managing a Network Node".
APPN uses LU 6.2 protocols to provide peer connectivity between
CP-CP session partners. The router network node implements the LU
6.2 protocols required for CP-CP sessions and those used in sessions
between a network node CP and its network management focal point. The
router implementation of APPN does not provide an application program
interface to support user-written LU 6.2 programs.
Table 1. Implementation of APPN Network Node Functions
| APPN Function | Yes | No | Notes |
|---|---|---|---|
| Session services and supporting functions |
|
|
|
| Multiple CP-CP sessions | X |
|
|
| Mode name to class of service (COS) mapping | X |
| 1 |
| Limited resource link stations | X |
| 2 |
| BIND segmentation and reassembly | X |
| 3 |
| Session-level security | X |
| 4 |
| Intermediate session routing |
|
|
|
| Intermediate session routing | X |
|
|
| Routing of dependent LU sessions | X |
|
|
| Fixed and adaptive session-level pacing | X | ||
| RU segmentation and reassembly | X | 5 | |
| Directory services |
|
|
|
| Broadcast searches | X |
|
|
| Directed searches | X |
|
|
| Directory caching | X |
|
|
| Safe storage of directory services cache | X | 6 | |
| Central directory server | X | 7 | |
| Central directory client | X | 7 | |
| Registration of APPN EN LUs with network node server | X |
|
|
| Definition of LEN node LUs on network node server | X | ||
| Use of wild cards to define attached LEN node resources | X | ||
| Accept multiple "resource found" conditions | X | ||
| Network node server for DLUR EN - Option set 1116 | X | ||
| Topology and routing services |
|
|
|
| Topology exchange | X | ||
| Periodic topology broadcasts | X | 8 | |
| Topology database maintenance | X | 9 | |
| Topology awareness of CP-CP sessions | X | ||
| Randomized route computation | X | 10 | |
| Cached routing trees | X | 11 | |
| Safe storage of topology database | X |
| |
| Garbage Collection Enhancements | X |
| |
| Connectivity |
|
|
|
| Connection network definition | X | 12 | |
| Multiple transmission groups | X | ||
| Parallel transmission groups | X |
| |
| Management services |
|
|
|
| Multiple domain support (MDS) | X | ||
| Explicit focal point | X | ||
| Implicit focal point | X | ||
| Held alerts | X | ||
| SSCP-PU sessions with focal points | X | ||
| SNA/MS problem diagnosis data in alerts | X |
Notes:
When the router generates a new routing tree, it stores that tree in a cache. When the router receives a service request, it checks this cache first to see if a route has been computed. Use of the cache reduces the number of route calculations required. When the router receives topology information that invalidates a routing tree, it discards the tree. The router recalculates the tree as needed and caches the new tree.
In addition to the base APPN Architecture functions, the router also implements the following option set towers and new functions:
HPR is an enhancement to APPN architecture that provides better performance over high speed, low error rate links using existing hardware. HPR replaces the normal APPN intermediate session routing (ISR) with a Network Control Layer (NCL) containing a new type of source routing function called automatic network routing (ANR). The complete HPR route is contained in the ANR packet allowing intermediate routing nodes to route the packets with less processing overhead and storage.
HPR also eliminates the error recovery and flow control (session-level pacing) procedures for each link between nodes and moves the error recovery and flow/congestion control procedures to the end-points of an HPR connection. A transport layer using a new error recovery procedure called Rapid Transport Protocol (RTP) is used by the endpoints of the HPR connection. HPR intermediate nodes have no session or RTP connection awareness. This new transport layer features:
The router implements both ANR routing and Rapid Transport Protocol. Therefore, the router can function both as an intermediate routing HPR node and as an HPR connection endpoint node.
HPR uses APPN network control functions including class of service (COS)-based least-weight route calculation and transmission priority. HPR interoperates seamlessly with APPN ISR:
APPN ISR uses the QLLC protocol for X.25 direct data link control, the IEEE 802.2 LLC Type 2 protocol for token-ring, Ethernet, PPP, and Frame Relay and SDLC protocol for the SDLC data link control. APPN HPR, which is supported on token-ring, Ethernet, PPP, and Frame Relay, does not use LLC Type 2 protocol, but does use some functions of an APPN link station for XID and inactivity timeout. A single APPN link station is therefore used for ISR or HPR. Different mechanisms are used to distinguish between ISR and HPR traffic depending upon the DLC type:
Each protocol that uses a port must have a unique SAP address, with the exception of DLSw (which may use the same SAP address as other protocols because DLSw frames will not be destined for the local MAC address, but rather a DLSw MAC address). A unique SAP address identifies the APPN link station for HPR traffic (Local HPR SAP address parameter). If ISR traffic is destined for a link station, then a different SAP address (Local APPN SAP address parameter) must be used. The ISR traffic uses LLC Type 2 LAN frames. The HPR traffic is handled in similar fashion to LLC Type 1 LAN frames and must have a different SAP address.
The default SAP address for HPR traffic is X'C8'. If X'C8' has already been used by another protocol on a port, the default must be overridden.
| Note: | There is only one APPN link station even though APPN ISR and HPR traffic use different SAP addresses. |
APPN ISR traffic and APPN HPR traffic transferred over a Frame Relay data link connection supports both the RFC 1490/2427 bridged frame format and the RFC 1490/2427 routed frame format.
APPN ISR traffic will be transferred over a Frame Relay data link connection using the connection-oriented multiprotocol encapsulation method defined in RFC 1490/2427 using:
APPN HPR traffic transferred over a frame-relay data link connection does not use IEEE 802.2 LLC. It uses a different multiprotocol encapsulation as defined in RFC 1490/2427 using:
APPN HPR does not use a SAP for traffic transferred using the RFC 1490/2427 routed frame format because there is no Layer 2 protocol.
APPN HPR uses a SAP for traffic transferred using the RFC 1490/2427 bridged frame format.
Refer to Table 3 for a list of DLCs that support HPR.
| Note: | HPR is not supported over SDLC, X.25, or DLSw ports. |
The DLUR option extends the support of T2.0 or T2.1 devices containing dependent LUs to APPN nodes. The DLUR function on an APPN network node or an APPN end node works in conjunction with a dependent LU server (DLUS) in a mixed APPN/subarea network. The DLUS function may reside in some other part of the mixed network from the DLUR.
The dependent LU flows (SSCP-PU and SSCP-LU) are encapsulated over an LU 6.2 (CP-SVR) pipe established between the DLUR APPN node and the DLUS SSCP. The CP-SVR pipe is made up of a pair of LU 6.2 sessions using a new CPSVRMGR mode between the DLUR and the DLUS. This pipe brings the SSCP function (in the DLUS) to the DLUR APPN node where it can be made available to attached T2.0/T2.1 nodes containing dependent LUs.
The dependent LU will appear to be located within the domain of the serving SSCP. Session initiation flows will be emulated from the DLUS, but session bind and data paths will be calculated directly between the dependent LU and its session partner. This path may or may not traverse the serving DLUS node.
Set the adjacent node type parameter to PU 2.0 Node when defining a link station to a T2.0 adjacent node containing dependent LUs. Set the adjacent node type parameter to APPN end node or LEN end node when defining a link station to a T2.1 adjacent node containing dependent LUs.
See Table 3 for the types of ports providing connection to the downstream PU (DSPU) that are supported.
The APPN DLUR option includes the following functions:
The DLUR option, as implemented on the router network node, has the following functional restrictions:
The following are example VTAM Switched Major Node definitions for DLUR. You should note that PATH statements are necessary only if VTAM is initiating the connection to the DSPU.
You should refer to VTAM Resource Definition Reference SC31-6427, for details of the DLC parameter statements for the Switched Major Node definitions.
DABDLURX VBUILD TYPE=SWNET,MAXGRP=400,MAXNO=400,MAXDLUR=20 ************************************************************************ *IN THE DLCADDR, THE 'SUBFIELD_ID' = CV SUBFIELD OF THE CV91 * * MINUS 0X90. * *FOR EXAMPLE, THE CV94 SUBFIELD IS CODED ON DLCADDR=(4,X,... * ************************************************************************ ************************************************************************ * Following are PU Statements for 2.0 and for 2.1 ************************************************************************ ************************************************************************ * 2.0 PU STATEMENT ************************************************************************ *PU20RT PU ADDR=05,PUTYPE=2,MAXPATH=8,ANS=CONT,USSTAB=AUSSTAB, * ISTATUS=ACTIVE,MAXDATA=521,IRETRY=YES,MAXOUT=7, * PASSLIM=5,IDBLK=017,IDNUM=00035,MODETAB=AMODETAB * LOGAPPL=ECHO71,DLOGMOD=M23278I(1) ************************************************************************ * Path statements are not required if the DSPU is initiating the * connection to VTAM ************************************************************************ *PU20LU1 LU LOCADDR=2 (11) *PU20LU2 LU LOCADDR=3 *PU20LU3 LU LOCADDR=4 ************************************************************************ * 2.1 PU STATEMENT ************************************************************************ *PU21RT PU ADDR=06,PUTYPE=2,CPNAME=PU21RT,ANS=CONT,MAXPATH=8, * ISTATUS=ACTIVE,USSTAB=AUSSTAB,MODETAB=AMODETAB * LOGAPPL=ECHO71,DLOGMOD=M23278I (1) ************************************************************************ ************************************************************************ * * Following are examples of path statement coding for various * DLC types. * * There is no difference in the path statement definitions * between a PU 2.0 and a PU 2.1 * * Path statements are required if VTAM is initiating the connection * to the DSPU. * ************************************************************************ ************************************************************************ * Below is SDLC ************************************************************************ *A20RT PATH PID=1, * DLURNAME=GREEN, * DLCADDR=(1,C,SDLCNS), * DLCADDR=(2,X,5353), (2) **port name * DLCADDR=(3,X,C1) (3a)**station address
************************************************************************ * Below is Frame Relay ************************************************************************ *A20RT PATH PID=2, * DLURNAME=GREEN, * DLCADDR=(1,C,FRPVC), * DLCADDR=(2,X,4652303033), (2)**port name * DLCADDR=(3,X,04), (3)**SAP address * DLCADDR=(4,X,0024) (4)**DLCI ************************************************************************ * Below is Frame Relay BAN ************************************************************************ *A20RT PATH PID=3, * DLURNAME=GREEN, * DLCADDR=(1,C,FRPVC), * DLCADDR=(2,X,4652303033), (2)**port name * DLCADDR=(3,X,04), (3)**SAP address * DLCADDR=(4,X,0024), (4)**DLCI * DLCADDR=(6,X,400000000001) (5)**MAC addr ************************************************************************ * Below is DLSw ************************************************************************ *A20RT PATH PID=3, * DLURNAME=GOLD, * DLCADDR=(1,C,TR),(7) * DLCADDR=(2,X,444C53323534),(2)**port name * DLCADDR=(3,X,04), (3)**SAP address * DLCADDR=(4,X,400000000001) (6)**MAC address * ************************************************************************* ** Below is Token Ring ************************************************************************* *PATHT20 PATH PID=1, * DLURNAME=RED, * DLCADDR=(1,C,TR), * DLCADDR=(2,X,5452303030), (2)**port name * DLCADDR=(3,X,04), (3)**SAP address * DLCADDR=(4,X,400000011088) (6)**MAC address ************************************************************************* ** Below is Ethernet ************************************************************************* *PATHE20 PATH PID=1, * DLURNAME=PURPLE, * DLCADDR=(1,C,ETHERNET), * DLCADDR=(2,X,454E303030), (2)**port name * DLCADDR=(3,X,20), (3)**SAP address * DLCADDR=(4,X,400000011063) (6)**MAC address
************************************************************************ * Below is X25 SVC ************************************************************************ *A20RT PATH PID=3, * DLURNAME=GREEN, * DLCADDR=(1,C,X25SVC), * DLCADDR=(2,X,583235303033), (2)**port name * DLCADDR=(4,X,C3), (8)**Protocol identifier * DLCADDR=(21,X,000566666),(9)**Destination DTE address ************************************************************************ * Below is X25 PVC ************************************************************************ *A20RT PATH PID=3, * DLURNAME=GREEN, * DLCADDR=(1,C,X25PVC), * DLCADDR=(2,X,583235303033), (2)**port name * DLCADDR=(3,X,0001) (10)**Logical channel number ************************************************************************
************************************************************************ ************************************************************************ * LU statements ************************************************************************ ************************************************************************ *PU21LU1 LU LOCADDR=2 (11) *PU21LU2 LU LOCADDR=3 *PU21LU3 LU LOCADDR=4 ************************************************************************
| Notes: |
|
See "TN3270E Server" for an example of an internal PU path statement.
When nodes are attached to a shared-access transport facility (SATF), any-to-any connectivity is possible. This any-to-any connectivity allows direct connections between any two nodes, eliminating routing through intermediate network nodes and the corresponding data traversing the SATF multiple times. To achieve this direct connectivity, however, TGs must be defined on each node for all the other possible partners.
Defining connections between all possible pairs of nodes attached to the SATF results in a large number of definitions (increasing on the order of the square of the number of nodes involved) and also a large number of topology database updates (TDUs) flowing in the APPN network. To alleviate these problems, APPN allows nodes to become members of a connection network to represent their attachment to an SATF. Session traffic between two nodes that have been defined as members of a connection network can be routed directly, without passing through a network node (achieves direct connectivity). To become a member of a connection network, an APPN node's port must be "attached" to a Connection Network by defining a connection network interface. When the port is defined, a Connection Network TG is created by the APPN component to identify the direct connection from the port to the SATF (i.e. the connection network). This TG is not a conventional TG as in the case of defined link stations, but rather represents the connection to the Connection Network in the topology database.
| Note: | TGs for end nodes are not contained in the network topology database, but are contained in the node's local topology database. TDUs do not flow through the network when a connection is established through a Connection Network or when an end node is made a member of a Connection Network. |
Because the connectivity is represented by a TG from a given node to a Connection Network, normal topology and routing services (TRS) can be used for the network node server to calculate the direct path between any two nodes attached to the SATF (with TGs to the same Connection Network). DLC signaling information is returned from the destination node during the normal locate process to enable the origin node to establish a connection directly to the destination node.
Therefore, to achieve direct connectivity on an SATF, instead of each node on the SATF being defined (or connected) to each other, each node is connected to a Connection Network. The Connection Network is often visualized as a virtual node on the SATF to which all other nodes are attached. This model is frequently used and, in fact, the term Virtual Routing Node (VRN) is often interchanged with the term Connection Network.
When a connection network is defined, it is named. This name then becomes the CP name of the VRN and must follow all the requirements of any CP name. See Table 24 for a list of these requirements.
The Branch Extender (BrNN) function is designed to optimize the connection of a branch office to an APPN WAN backbone network. The BrNN isolates all the end nodes on one or more branch office LANs from the backbone WAN. The domain of a BrNN may contain only end nodes and cascaded BrNNs. The domain of a BrNN does not contain network nodes or nodes with DLUR.
When configuring a BrNN, configure link stations to the backbone to be uplinks. This causes the BrNN to appear as a conventional end node to the backbone. From the perspective of the backbone, all resources in the domain of the BrNN appear to be owned by the BrNN, hiding the topology of the BrNN's domain from the backbone and reducing the number of broadcast locates in the backbone.
A BrNN presents a conventional network node interface over downlinks. End nodes in the domain of the BrNN register their resources with the BrNN and use the BrNN as a conventional network node server.
A BrNN accomplishes:
The following are limitations of Branch Extender:
Extended Border Nodes (BNs) allow networks with different network IDs to connect to one another. CP-CP sessions will be established across the network boundaries, and directory services flows and session establishment will be allowed to span the interconnected networks. Topology information will not be exchanged across the network boundary. This allows networks with different network IDs to establish CP-CP sessions and provides topology isolation between different networks.
In addition to allowing networks with different network IDs to interconnect, BNs provide a mechanism to subdivide networks with the same network ID into smaller "topology subnetworks". This subdivision provides topology isolation between the two subnetworks while allowing directory services flows and sessions to span the subnetwork boundaries.
There must be a BN on one side of the subnetwork boundary in order to use this function. When a BN connects to a non-native NN, the BN looks like an EN to the non-native NN, even though the BN is actually a NN.
There may be two BNs, one on each side of the boundary, cooperating to perform this function. When two BNs connect across a subnetwork boundary, the BN will look like a NN to the non-native BN.
A BN will appear to be the NN server for all non-native resources accessible through the BN. This allows the existing APPN directory caching and route calculation functions to work, while enabling the BN to intercept and modify all Locate and BIND flows which cross an inter-subnetwork TG (ISTG).
BNs implement piece-wise optimal session route calculation. Each subnetwork calculates its own part of the session's route selection control vector (RSCV) to the entry point in the next non-native subnetwork. While the RSCV will be optimal through the native subnetwork, there is no guarantee that the end-to-end session path will be optimal.
Figure 1 shows many of the connectivity options provided by the BN function. In general, you can get from any network to any other network except that NetF can only reach network NetE and NetE is the only network that can reach NetF.
Figure 1. Extended Border Node Connectivity
|
| Note: | Solid lines represent intersubnetwork TGs. |
In this figure:
The SSE function of a router is enabled when the router is enabled for APPN. This is true even if the Extended Border Node function is not enabled. This means that the router may act as the network node server for a VTAM end node. As such, it can handle NNS functions for end nodes requesting SLU-initiated sessions, third part initiated sessions, session request queuing, automatic login, session-release requests, and EN TG vector registration.
The SSE function is not used when the router is acting as a Branch Extender since down stream VTAMs are not allowed in that configuration.
There are no requirements for other APPN nodes in a network as long as they are not directly connected to a BN across a topology boundary. APPN nodes that are connected to a BN across a topology boundary (across an ISTG) must meet one of these requirements:
Nodes attached using ISTGs that do not meet either of these requirements will generate alerts and do not handle some of the new flows associated with BNs. However, if other paths through the network are available, you may still have end-to-end connectivity.
Both Branch Extender and Extended Border Nodes serve to minimize network topology. The choice of which to use depends upon the network.
A branch extender is the appropriate choice when you have a single network with one or more groups of end nodes where each group of end nodes typically needs to communicate with other end nodes in that group, and only occasionally need to interact with the backbone network.
None of the devices downstream from the branch extender may be network nodes, DLUR, VTAM, or VTAM end nodes.
With the branch extender in place the backbone network's view of the branch extender is as a giant end node with all the downstream LUs being owned by this giant end node. The backbone has no knowledge of the topology downstream from the branch extender, thus reducing the overhead of topology exchanges. Conversely, the branch extender's network node server, which is part of the backbone, will have knowledge of all the LUs owned by the branch extender if the branch extender is configured to register resources. This serves to reduce the number and size of broadcast searches and topology updates.
An extended border node is the appropriate choice when you have multiple networks you want to tie together, or when you have a large network you want to subdivide without restriction on what node types are allowed in the subdivided pieces. There is no concept of upstream or downstream and you can have additional extended border nodes, network nodes, end nodes, DLUR, VTAM, or VTAM end nodes located anywhere in your network. Unlike the branch extender, an extended border node cannot register resources with another network.
The router network node can act as an APPN entry point that forwards APPN-related alerts to an APPN focal point. APPN focal points may be defined explicitly or implicitly.
You can use SNMP to access these IETF standardized MIBs:
You can also use SNMP to access these enterprise-specific MIBs:
The router network node can serve as an APPN entry point for alerts related to the APPN protocol. As an entry point, the router is responsible for forwarding APPN and LU 6.2 generic alerts about itself and the resources in its domain to a focal point for centralized processing. A focal point is an entry point that provides centralized management and control for other entry points for one or more network management categories.
| Note: | If a focal point is not available to receive an alert from the device, the alert is held (stored) by the device. |
Entry points that communicate with a focal point make up that focal point's sphere of control. If a focal point explicitly defines the entry points in its sphere of control and initiates communication with those entry points, it is an explicit focal point. If a focal point is designated by its entry points, which initiate communication with the focal point, the focal point is an implicit focal point. The focal point for the router can be either an explicit or implicit focal point.
Routers configured as branch extender nodes have additional flexibility. As with conventional network nodes, the focal point can directly establish an explicit relationship with the branch extender node. Also as with conventional network nodes, you can configure one or more implicit focal points at the branch extender node.
Unlike conventional network nodes, branch extender nodes can alternatively learn of the focal point from its network node server. When the network node server establishes a relationship with the focal point, either explicitly or implicitly, it will notify all its served end nodes, including served branch extender nodes, of the focal point name.
If the session between the router entry point and its primary focal point fails, the router can initiate a session with a designated backup focal point. Before initiating a session with a backup focal point, the router entry point makes an attempt to reestablish communication with its primary focal point if the router has been assigned session re-establishment responsibility. If that attempt fails, the router switches to the backup focal point.
| Note: | The router will attempt to establish a session with the backup focal point, or will attempt to re-establish the session with the primary focal point, only if the router has an alert to send. |
After switching to a backup focal point, the router will periodically attempt to re-establish its session with the primary focal point. The interval between attempts is doubled each time an attempt fails until a maximum interval of one day is reached. From that point on, the attempt is performed daily.
Notes:
The router entry point communicates with the focal point through an LU 6.2 session. Multiple-domain support (MDS) is the mechanism that controls the transport of management services requests and data between these nodes. The router network node does not support SSCP-PU sessions with focal points.
Management processes within the router's control point are handled by its control point management services (CPMS) component. The CPMS component within the router network node collects unsolicited problem management data from resources within the router's domain and forwards this data to the appropriate focal point.
The router network node uses the following message units for sending and receiving management services data, including alert messages from domain ENs:
An operator or application at an SNMP network management station can query objects in the APPN MIBs (using the SNMP get and get_next commands) to retrieve APPN status information and node statistics. A subset of APPN MIB objects can be modified using the SNMP set command. The APPN MIBs can be accessed only using SNMP.
Information flows between APPN NNs to inform the NNs about network resources. Each NN keeps a topology database consisting of the names and characteristics of those resources. When a resource is eliminated from the network, it can also be deleted from each NN topology database. When a NN detects that a resource in its topology database is obsolete, the node will broadcast information stating that the resource should be garbage-collected. If NNs receiving this information support Enhanced Garbage Collection, they should delete that resource from their topology database. The record is not actually garbage-collected until the next garbage collection cycle. A NN examines each resource in its topology database once a day.
The configurable held alert queue function allows you to configure the size of the held alert queue. If a focal point is not available, the held alert queue saves APPN alerts. When a focal point becomes available, the held alerts are sent. If more alerts arrive than can be held, the oldest alerts are discarded.
| Note: | If you configure a large value for the Held Alert Queue Size, the extra memory should be accounted for. You can do this by letting the tuning algorithm automatically calculate the Maximum Shared Memory value. See "APPN Node Tuning" for additional information about the node tuning algorithm. |
A focal point is a node with centralized management responsibility. The managing node can contact the managed node (router) and establish a management session. The managing node is then an explicit focal point. When the name of the managing node is configured at the router and the router can initiate a management session, the managing node is an implicit focal point. You can configure a single, primary implicit focal point with up to eight backup implicit focal points, where each focal point is a fully qualified network name. The router will attempt to contact each focal point in order until a successful management session is established.
If the management session is with a backup implicit focal point, the device will periodically attempt to reestablish its session with the primary implicit focal point. The interval between attempts is doubled each time an attempt fails until a maximum interval of one day is reached. From that point on, the attempt is performed daily.
| Note: | If an explicit focal point initiates a management session with a device, it will cause a session with an implicit focal point to terminate. |
The dynamic definition of dependent LUs (DDDLU) is a VTAM facility that allows the logical units to be known by VTAM when they connect to VTAM, rather than during the major node activation of the related PU. With this support, VTAM builds LU definitions from reusable model LU definitions instead of using predefined LUs. The LU definitions are replaced or changed each time the device containing the LU(s) powers on (or notifies that it is enabled and startable).
The DDDLU capability requires some minor changes in VTAM and depends on the activation of the physical unit (PU) being done by a format-1 ACTPU. This format-1 ACTPU can carry the PU Capabilities Control Vector . The PU Capabilities Control Vector will tell whether the sending node supports unsolicited NMVTs (network management vector transport) for Reply Product Set ID (PSID). If unsolicited NMVTs for Reply PSID are supported, DDDLU can be achieved.
The Reply PSID NMVT contains the local address of each LU, a power on/off indicator, the machine type and model number of the device, and optionally other device-dependent information needed to define the logical units. VTAM uses this information to choose an appropriate model LU definition statement to build an LU definition.
NMVT vectors are shown in Table 2.
| Device/Model | NMVT Vector |
|---|---|
| 3270 mod 2 display | 3270002 |
| 3270 mod 3 display | 3270003 |
| 3270 mod 4 display | 3270004 |
| 3270 mod 5 display | 3270005 |
| 3270 printer | 3270P |
| SCS printer | SCSP |
The previous section discussed dynamic definition of dependent LUs when initiated by the PU via NMVTs. Dynamic dependent LU definition may also be driven by the host. In this case, no dependent LUs need to be configured. The only requirement is that the link station or local PU be configured to allow dynamic LU definition. For host-intiated dynamic LU definition, the dependent LUs must be defined in the host major node file and INCLUD0E=YES must be specified (for subarea PUs) on the PU statement. INCLUD0E keyword is supported by VTAM V4R4 with APARs OW31805 and OW31436. For remote subarea connections through NCP, V7R6 is needed for INCLUD0E keyword support.
As the ACTLU requests are processed, the LUs will be created using the name from control vector 0E. This greatly reduces configuration time for dependent LUs. If the host is a DLUS and the PU is being serviced by a DLUR in another node, then CV0E of the ACTLU request may not be forwarded to the PU from the DLUR. In this case, the LUs will not be created dynamically. Once LUs have been created dynamically, they can only be removed by rebooting or manually deleting via configuration. If the LU names are changed in the host major node file after the LUs have been created dynamically, the local names will not be changed.
The TN3270E Server provides a TN3270 gateway function for TN3270 clients that are downstream of a SNA host running a 3270 application. These clients connect to the server using a TCP connection. This connection is mapped to a SNA dependent LU-LU session that the server maintains with the SNA host. The TN3270E Server handles the conversion between the TN3270 datastream and a SNA 3270 datastream. The TN3270E Server function complies with RFC 1646 and RFC 1647.
TN3270 sessions can span APPN networks as well as IP networks using the HPR over IP.
The TN3270E Server can use a subarea connection or the APPN DLUR function to communicate with the host.
See "Support for Subarea SNA Connections from the TN3270E Server to the Host" for more information and see "Configuring TN3270E Using DLUR" and "Configuring TN3270E Using a Subarea Connection"for sample configurations.
If you are using DLUR to communicate with the host, the local PUs used by the TN3270E Server need to be configured in the host as DLUR internal PUs. The following code is an example of the host VTAM configuration:
*
PUJOE7 PU ADDR=12,
IDBLK=077,IDNUM=EEEE7, (1)
MAXPATH=8,
ISTATUS=ACTIVE,
MODETAB=LMT3270,
USSTAB=STFTSNA2,
ANS=CONT,
MAXDATA=521,
IRETRY=YES,
MAXOUT=7,
DLOGMOD=G22NNE,
NETID=STFNET,
PASSLIM=5,
PUTYPE=2
JCPATH7 PATH PID=1,
DLURNAME=VLNN01,
DLCADDR=(1,C,INTPU),
DLCADDR=(2,X,077EEEE7)
JC7LU2 LU LOCADDR=2
JC7LU3 LU LOCADDR=3
JC7LU4 LU LOCADDR=4
JC7LU5 LU LOCADDR=5
JC7LU6 LU LOCADDR=6
| Note: |
There are two Telnet servers in the device, the remote console and the TN3270E Server. One IP address will be designated as the TN3270E Server address/port. Telnets to this address/port will be tn3270, and will not get to the remote console. The TN3270E configuration includes the TN3270E config> set command to configure the IP address/port for the TN3270E Server.
Only one address can be specified as the TN3270E address.
There can be any number of addresses assigned to an interface. If the system administrator does not want to lose the ability to Telnet to the router using an existing interface address, an additional address (with a subnet mask which RIP and OSPF will advertise) can be added to an interface. We recommend designating an interface address as the TN3270E Server Address.
For TN3270 purposes, this address is like an interface address.
This address is advertised over all dynamic routing protocols. It is also continually reachable, whereas interface addresses are only reachable when the interface is up. This address is not recommended as the TN3270E Server Address, except in cases where reachability is guaranteed without respect to the (up or down) state of any interface.
LU pooling is an enhancement to the TN3270E Server function that makes it easier to configure some TN3270E Server networks. This function allows SNA LUs to be grouped into named "pools". TN3270E clients can then request a connection using the pool's name as an LU name. The TN3270E Server will then choose an LU from the specified pool to service the client's request.
A pool is a logical group of LUs. These LUs can be from different PUs or the same PU, different Host or same Host, etc. When a client specifies a specific pool name, any LU from the pool may be selected.
There is always at least one implicit workstation pool. This pool is referred to as the global default pool. The name of this Pool is defined via the TN3270E config> set command. LUs must be added to this pool via the TN3270E config> add lu or TN3270E config> add implicit-pool command.
This enhancement allows users to define multiple TCP ports for the TN3270E Server to "listen" on. This support allows clients to specify the SNA resource they want using a port number.
When the ports are added, the user can define an LU pool to be associated with that port number. Clients that connect to this port and do not specify an LU name will be assigned an LU from this Pool. Note that the port will always be associated with an LU pool. By default, it will be associated with the global default pool.
An alternative to using the LU pool to port association for choosing an LU, is to use the TN3270E Server Client IP Address to LU Name Mapping which is discussed in "TN3270E Server Client IP Address to LU Name Mapping". If you enable the TN3270E Server Client IP Address to LU Name Mapping, then by default the LU is chosen using the LU Name Mapping rules rather than using the LU pool to port association. Therefore, by default, when LU Name Mapping is enabled, it applies to all ports. However, even when LU Name Mapping is enabled, it is possible to configure the port such that the LU Name Mapping function is ignored and the LU pool associated with the port is used to choose the LU.
TN3270E Server ports can also be defined for a particular type of TN3270 Server (Base or TN3270E) support. Since some base TN3270 clients do not negotiate properly with TN3270E Servers, a port can now be defined for these clients to connect to.
There should always be at least one port defined for use by the server. This port is specified via the TN3270E Config> set command.
There is always at least one port defined for use by the server. This port is specified via the TN3270E config> set command. The Pool associated with this port is always the global default pool.
The TN3270E Server Client IP Address to LU Name Mapping function provides a mechanism for administrators to control client access to the TN3270E Server's resources (ie LUs).
Mapping enhances central administration by allowing the administrator to configure which SNA resources(LUs/Pool) client IP address/subnets will map to and use without modifying client configurations.
Mapping removes the burden on the client of having to connect to a specific port or request a specific LU/Pool on their connect request. These decisions are maintained at the server.
When a client connects in while mapping is enabled, the Server will begin ANDing the client's IP address with the subnet mask of each map definition. The longest match between the incoming Client IP address and the map definition determines which map definition is tried first. If all eligible resources in the map definition are in use, the map definitions are again searched for the next most specific match.
If a map definition contains a full subnet mask (255.255.255.255), indicating that the entry is for a specific client, and a specific LU/Pool is not requested by the client, any LU/Pool in the map definition that matches the connection type may be tried.
If a map definition does not contain a full subnet mask and a specific LU/Pool is not requested, only Pool entries in the map definition will be tried. You must have the subnet map to a Pool. For individual workstation LUs with associated printers, only the workstation LU is required to be in the map definition.
A mixture of Pool and LU types(Workstation or Printer) can be added to a particular map. The resource selected will be based on the type of connection request. The order in which the resources are defined in the map will be the order in which it is chosen for a particular connection request.
When IP Address to LU Name Mapping is enabled, then by default client IP Address to LU Name Mappings rules apply to all ports. The client's IP address is used to determine which LU/Pool will be used. However, there are two ways to use the LU pool to port association while also having the LU Name Mapping function enabled.
In either case, the destination port number will be used to determine the SNA resource to use based on the table below. The table will also be used when Mapping is enabled, but no Map definitions exist.
If the client specifies an LU/Pool name on the connect request, that name must match a resource in a Map definition. If the name specified by the client is an LU name that is contained within a Pool, that LU name MUST be in the Map definition for the connection to be accepted. It is not sufficient for just an LU's Pool name to be in the Map definition.
When IP Address to LU Name Mapping is not enabled, the following table
describes how SNA resources are assigned.
| Client Connection | Port Definition | Result |
|---|---|---|
| Explicit LU or Pool name specified | Pool name defined | Explicit name is used as long as the incoming name matches the defined name. |
| Explicit LU or Pool name specified | <DEFLT> defined as Pool name | Explicit name is used as long as the incoming name has been defined |
| Explicit LU or Pool name specified | No Pool name defined on port | Explicit name is used as long as the incoming name has been defined |
| No resource name specified | Pool name defined | Name defined on port is used |
| No resource name specified | <DEFLT> specified as the Pool name | Global default Pool is used |
If prompted by VTAM, the TN3270E Server function will use DDDLU to create its local LUs in VTAM. Instead of sending all of the Reply PSID's when the ACTPU is received, the server will wait until the LU actually needs to be defined. The LU definition will occur when a TN3270 client connects in and needs an LU that has not been defined to VTAM.
Dependent LUs that are created dynamically when ACTLU requests are processed are available to the TN3270E server as workstation LUs. TN3270E Server configuration time is greatly reduced with the dynamic LU definition feature. However, the TN3270 workstation client must explicitly request the LU name; these LUs do not belong to an LU pool and are not available to printer clients. The dynamic dependent LUs are not available to the TN3270E Server Client IP Address to LU Name Mapping function. Only LUs that are configured may be used with the mapping function.
Connecting to a host for establishing an dependent LU-LU session can be accomplished using a traditional subarea connection or using an APPN connection in conjunction with the APPN DLUS/DLUR function. The APPN DLUS/DLUR solution allows the node to appear to VTAM as multiple PU devices, each supporting up to 253 dependent LUs. A node wishing to provide TN3270E Server services over a subarea connection for more than 253 clients simultaneously must also appear as multiple PUs to an attached host.
Subarea connections are supported over the following DLC types:
| Note: | Support for Subarea SNA connections for TN3270E Server services eliminates the need for APPN in the host. However, APPN must still be configured in the router. |
A subarea-attached SNA node configuration with a device performing the TN3270E Server function and appearing to VTAM as multiple downstream PUs is shown in Figure 2.
Figure 2. Multiple PUs for Subarea Connected SNA Nodes
 |
See "Configuring TN3270E Using a Subarea Connection" for a configuration example.
Enterprise Extender support for HPR over IP allows HPR/APPN applications to run over an IP backbone network and still take advantage of APPN Class of Service. HPR over IP encapsulates HPR data into a UDP/IP packet for delivery over the IP network.
Table 3 shows the DLC ports supported by the device
over APPN:
Table 3. Port Types Supported for APPN Routing
| Port Type | Standard | HPR | ISR | DLUR* |
|---|---|---|---|---|
| Ethernet | Version 2 | Yes | Yes | Yes |
| Ethernet | IEEE 802.3 | Yes | Yes | Yes |
| TR | 802.5 | Yes | Yes | Yes |
| Serial PPP |
| Yes | Yes | No |
| Serial FR (bridged and routed) ** |
| Yes | Yes | Yes |
| Frame Relay BAN |
| Yes | Yes | Yes |
| Serial LAN bridging |
| NA | NA | NA |
| SDLC |
| No | Yes | Yes |
| X.25 | CCITT X.25 | No | Yes | Yes |
| DLSw (remote only) *** |
| No | Yes | Yes |
| APPN/PPP/ISDN |
| Yes | Yes | No |
| APPN/FR/ISDN |
| Yes | Yes | Yes |
| APPN/PPP/V.25bis |
| Yes | Yes | No |
| APPN/PPP/V.34 |
| Yes | Yes | No |
| LANE | Forum compliant | Yes | Yes | Yes |
| ATM |
| Yes | No | Yes |
| HPR over IP |
| Yes | No | Yes |
| 100Mbps Ethernet |
| Yes | Yes | Yes |
| 100Mbps TR | 802.5 | Yes | Yes | Yes |
Notes:
This section describes the router configuration process and includes details about parameters.
APPN routing is configured on the individual adapters supporting the DLC desired. To use APPN routing, at least one of the following DLCs must be configured and enabled:
You can configure the router as an APPN network node in one of three ways, depending on the level of connectivity you desire with other nodes.
This group of APPN configuration steps:
If you choose the minimum configuration steps, adjacent nodes must define connections to the router network node to ensure connectivity. Because APPN nodes can initiate CP-CP sessions with the router network node, these nodes do not need to be defined in the router's configuration. In general, when configuring APPN on the router, you can simplify the task considerably by allowing the router network node to accept connection requests from any node. Configuring the network node in this manner eliminates the need to define information about adjacent nodes, except in the following cases:
In these cases, you must specify information about the adjacent node when enabling APPN routing on the specific port you are using to connect to the adjacent node, and should follow the configuration steps described in "Initiate Connections Configuration".
Use the following procedure for minimum configuration steps:
| Note: | Since Service Any is enabled by default, the node accepts any request for a connection that it receives from another node. |
Notes:
This group of APPN configuration steps:
Because APPN nodes can initiate CP-CP sessions with the router network node, these nodes do not need to be defined in the router's configuration, except in the following cases:
If neither of these cases apply to your configuration, you should follow the configuration steps described in "Minimum Configuration".
Use the following procedure for initiate connections configuration :
| Note: | Since Service Any is enabled by default, the node accepts any request for a connection that it receives from another node. |
| Note: | Link stations do not have to be defined on every port, only those over which you want to initiate connections to adjacent nodes. |
This group of APPN configuration steps:
This configuration provides a higher level of security because you explicitly define which APPN nodes may communicate with this router network node. A connection request from an adjacent node will be accepted only if its fully qualified CP name parameter has been configured on this network node. This group of configuration steps optionally enables you to have a secure link with each adjacent node by configuring the session level security feature for each link.
Use the following procedure for the controlling connections configuration:
Specify the following link station parameters:
To configure Branch Extender, set the following configuration parameters as appropriate for your network.
To configure extended border node you must configure one or more of these parameters:
The previously existing prompt used to enable branch extender has been expanded to allow you to choose the branch extender function, the extended border node function, or neither. Only if you enable the extended border node function will any of the other extended border node prompts appear.
Subnetwork visit count is the first prompt. This parameter defines the maximum number of topology subnetworks a session may span. The value defined here is used as the default value for the extended border node. You can specify different values for the subnetwork visit count when adding ports, links, or routing lists.
Cache search time is the next node level prompt. This specifies the number of minutes the extended border node will retain information on multi-subnetwork searches. The intention is for this to be the primary mechanism for limiting the size of this cache. However, the next parameter can also be used to control the size of this cache.
Maximum search cache size is next. This controls the same data structure controlled by the previous parameter. If set to zero, the maximum size is unlimited. Entries will be discarded only after the search cache time has expired. If you prefer to have a fixed maximum size for the search cache then specify that here. If this maximum is reached before any entries exceed the time limit the least recently entries are discarded.
List dynamics is the next prompt, and it allows you to control how the extended border node determines possible next hops when attempting to locate resources (LUs). The temporary list of possible next hop CPs is built dynamically by the operational code whenever the border node is attempting to locate a resource. This parameter specifies source(s) of next hop CP name(s) the extended border node may use to build this temporary dynamic list of CP names.
After the temporary list is built, it is always ordered so that configured next-hop CPs are first followed by CPs associated with similarly named known resources. Additional reordering may be performed. Once all the reordering is complete, the extended border node starts searching for the target resource one CP after another.
Note that once the extended border node actually locates a resource it will remember the next hop CP and always use that next hop CP for that particular resource, ignoring the routing lists. Entries from this table of located resources can be quite long lived. They are discarded if the table reaches its maximum size, a later search to that CP fails to locate the resource, or if search from that LU comes from a different CP.
The list dynamics parameter is set to one of the following values. It is possible to respecify this value for individual routing lists when, and if, you configure individual routing lists.
Note that if an LU name does not appear in a routing list the LU will not be reachable by the extended border node when this list dynamics parameter is set to none.
None of these dynamically obtained next-hop CP names are permanently saved with the configuration data. The list is recreated whenever a resource needs to be located.
If List optimization is enabled, the reordering process described in *** is repeated a second time and the CP names obtained from configured data are also eligible to be reordered.
If extended border node is enabled, two additional prompts are presented when you invoke the add port menu item. Both of these new items establish the default for analogous parameters at the link level. The values of these parameters at the link level determine link station behavior.
Subnetwork visit count is the first of these, and describes the same concept as defined at the node level. When a port is first configured this parameter is initialized to the node setting. With this parameter you allow individual ports to deviate from the node level setting.
Adjacent subnetwork affiliation is controlled by the other new extended border node prompt. This allows you to define whether or not the adjacent node is in the same network as the extended border node. The value specified here will be used as the default value for all links through the port. Allowed values are:
If extended border node is enabled the same two additional prompts are presented when you invoke the add link menu item as were previously presented under add port.
Subnetwork visit count and adjacent subnetwork affiliation are the same concept as defined at the port level. They are initialized to the corresponding port setting when a link is first configured. You change the value here if you want different links to have different values even though they are on the same port.
| Note: | Routing lists are not supported for 2210 12x models. |
A configured routing list allows you to explicitly define one or more possible next hop CPs for one or more destination resources (LUs). A wildcard character "*" may be used when defining the LU names to reduce the amount of configured data. You can also vary some of the node level defaults for a given routing list.
You can define multiple routing lists. Typically a group of LUs with similar routing requirements would be configured into a single routing list. Additional groups of LUs, each group with its own routing requirements, would be configured into additional routing lists.
There are limits on the number of LU names and number of CP names used in routing lists. These limits vary according to the model router you have. See Table 38 for the configuration command detail. Limits have been set to allow as much flexibility as possible in various environments. The ability of the router to handle the specification of many routing lists, each with many LU names and CP names, is limited by the availability of configuration nonvolatile memory, router memory, and APPN shared memory. See "APPN Node Tuning" for a discussion of the APPN tuning parameters which control the amount of shared memory.
Recall from the discussion under the set node prompt that configured routing lists are never modified by operational code. When the extended border node uses a given routing list it copies the next hop CP names into a temporary routing list. This temporary dynamic routing list is augmented with dynamic entries as allowed by your configuration setting of the list dynamics parameter. This temporary list is short lived, and is discarded once the destination resource is found or the list is exhausted.
The routing list name is the first prompt you see when adding or modifying a routing list. This name is not used by the operational code at all. It's purpose is to allow you to identify a specific routing list if you want to modify it or delete it at some later time.
Subnetwork visit count and list optimization are the next two prompts, and follow the same concept as the analogous parameters defined at the node level. A new routing list initializes these values with the current node level settings. You change these values for individual routing lists as your requirements dictate.
Destination LU prompt(s) are next. Here you may configure at least one, and optionally more, destination resources. Any of the FQLU names may be prematurely terminated with a trailing wildcard "*" to identify a group of LUs. You may not imbed a "*" in the middle of an FQLU name.
One of your routing lists may specify a standalone "*" as one of the destination LUs. If this is done then that routing list is known as the default routing list, and this default routing list will be used by the extended border node for all destination LUs that don't better match the LUs specified in the other routing lists. This list is also used to find LUs when INAUTHENTIC NETID is indicated.
When modifying an existing routing list with many LU names the process of stepping through the LU names could be quite tedious. There are a number of shortcut keys defined to help speed stepping through an existing list of names. Those shortcut keys are defined in the section with the configuration command detail.
Routing CP prompt(s) are the last part of entering a routing list. Here you supply the names of one or more CPs that may know how to reach the configured list of LUs. Along with each CP name you may configure an optional subnetwork visit count. This allows you to specify a different maximum number of subnetworks a session may traverse for different CPs.
In addition to explicitly configuring FQCP names there are a couple keywords defined that equate to the local node's CP name, all native extended border nodes, etc. See the section with configuration command detail for those keywords.
As with the LU name list, the same shortcut keys are available to speed stepping through an existing CP name list.
| Note: | COS mapping tables are not supported for 2210 12x models. |
The class of service mapping table allows for the conversion of non-native COS names to native COS names and vice versa. Non-native networks using the same COS names as the extended border node's native network need not have a COS mapping table defined. If only some of the non-native COS names differ from the native COS names, then only those that differ should be configured in a COS mapping table.
A given COS mapping table may apply to a single or multiple non-native networks. You may configure multiple COS mapping tables as necessary.
There are limits on the number of non-native network names used in COS mapping tables. These limits vary according to the model router you have. See Table 39 for the configuration command detail. Limits have been set to allow as much flexibility as possible in various environments. The ability of the router to handle the specification of many COS mapping tables, each with many non-native network names and COS name pairs, is limited by the availability of configuration nonvolatile memory, router memory, and APPN shared memory. See "APPN Node Tuning" for a discussion of the APPN tuning parameters which control the amount of APPN shared memory.
COS mapping table name is the first prompt. As with the analogous name for routing lists, this parameter is not used by the operational code. It's purpose is to allow you to refer to a specific COS mapping table so that you can modify or delete it. Different COS mapping tables must have different names, but a given COS mapping table may have an identical name as a routing list.
Non-native CP name(s) are prompted for next. These are use to specify the non-native network(s) that this COS mapping table applies to.
As with LU names in a routing list, you may prematurely terminate any of the FQCP names at any point with a trailing wildcard "*" . This allows you to specify a range of non-native FQCP names in one or more non-native networks. You may not imbed a wildcard in the middle of a FQCP name.
One COS mapping table in the extended border node may have a standalone wildcard "*" as one of the non-native CP names. Such a table is known as the default COS mapping table, and will be the table used by the extended border node whenever no other table has a CP name that matches the non-native network.
COS name pairs are the final part of configuring a COS mapping table. Here you are prompted for one or more pairs of COS names. Each COS name pair consists of a native COS name followed by the corresponding COS name used in the non-native network.
The extended border node uses this table to translate from native to non-native networks and vise versa. If you need to map multiple native COS names into a common non-native COS name you should configure one COS name pair for each possible mapping. Similarly you may need to map multiple non-native COS names into a common native COS name, and that too can be accomplished by configuring a COS name pair for each possible mapping. If there are multiple possible mappings in a table the extended border node will use the first exact mapping found.
Each COS mapping table may have one COS name pair where the non-native COS name is a wildcard "*" . This is the default COS mapping entry for that table, and it is used to translate all unrecognized non-native COS names into a single native COS name. Each COS mapping table may have one of these default COS mapping entries. You can never code a "*" as the native COS name.
See Table 3 for a list of ports that support HPR.
See "Configuration Requirements for APPN" for information about configuring the protocols that support APPN and HPR routing over direct DLCs on the router. In the case of HPR parameters such as retry and path switch timers, the configuration is done at the node level and is not specified on individual adapters.
See Table 3 for a list of ports that support DLUR.
Focal points can be explicit or implicit. Explicit focal points are configured at the focal point itself. No configuration at the router is required.
Implicit focal points on the other hand are configured at the router. You configure them with the command add focal_point. Add the primary implicit focal point first. If you add another focal point, it is known as the first backup implicit focal point. If you add yet another, it is known as the second backup implicit focal point. Up to eight backup implicit focal points may be added for a total of 9.
To delete a focal point use the command delete focal_point. You will be prompted for the name of the focal point to delete. When the name is deleted, the remaining focal points retain their relative position with each other. Subsequent focal points will be added at the end of the list.
There is no way to insert a focal point in the middle of the list. You must delete them one at a time and then re-enter the entire list.
To configure the size of the held alert queue enter the command set management and answer the Held Alert Queue Size question. The queue defaults to a size of 10 alerts, and valid values are from 0 through 255 alerts.
As you increase the size of the held alert queue, additional memory is needed. If you set it to a high value, you may want to adjust the "Maximum Shared Memory" value. See"APPN Node Tuning" for additional information.
When you configure APPN on the router, you can specify the Transmission Group (TG) characteristics for the link station that defines a connection between the router network node and an adjacent node. These characteristics, such as the security of a link or its effective capacity, are used by APPN when calculating an optimum or least-weight route between nodes in the APPN network.
APPN on the router uses a set of default TG characteristics for each port (or DLSw port). These defaults, defined by the default TG characteristics parameter apply to all the TGs for link stations defined on a port unless they are overridden for a particular link station by the modify TG characteristics parameter.
These default TG characteristics are also used for dynamic link stations established when an adjacent node requests a connection with the router network node, but does not have a predefined link station definition on the router network node. The Service any node parameter must be enabled.
You can change the following parameters using the router talk 6> interface as well as the Configuration Program:
The APPN route calculation function uses a COS definition for TGs which is a table containing rows of TG characteristic ranges. Each row defines a given range for each of the eight TG characteristics and the corresponding TG weight for that row. APPN starts at the top of the table and continues down the table until all eight of the TG characteristic parameter values fit within the ranges given for that row. APPN then assigns the weight of that row as the TG weight for that link. There is also a COS definition for nodes that calculates a node's weight. The route calculation function continues until it has found the path with the least combined weight of TGs and nodes. This is the least weight route.
As an example of how TG characteristics are used to influence the selection of a route through an APPN network node, suppose that a route from network node router A to network node router D can pass through either network node router B or router C. In this example, router A defines serial port PPP connections to both router B and router C. However, the connection from router A to router B is a 64-Kbps link, while the connection from router A to router C is a slower-speed 19.2-Kbps link.
To ensure that the higher-speed connection from router A to router B is viewed as the more desirable path for routing APPN interactive traffic, the effective capacity TG characteristic for the link station associated with this path would be modified. In this case, the default value for effective capacity is X'38', which correctly represents a link speed of approximately 19.2-Kbps. However, the effective capacity would be changed to X'45' to properly represent the 64-Kbps link. Since the effective capacity for the TG from router A to router B is now X'45', this path is assigned a lower weight in the COS file for interactive traffic. Consequently, the connection from router A to router B is represented as more desirable than the connection from router A to router C.
You can also change the TG characteristics if you purposefully want to favor certain TGs for route selection. In addition to the five architected TG characteristics, there are also three user-defined TG characteristics. You may define these user-defined TG characteristics in order to bias the route selection calculation in favor of certain paths.
| Note: | For DLSw ports the TG characteristics that you define effect only the selection of routes between APPN nodes over these DLSw ports. These characteristics have no direct effect on any intermediate routing performed by DLSw on APPN's behalf. |
You can use a template to create new user-defined COS names and associated definitions for TGs and nodes which can be used with new mode names or mapped to existing mode names.
In addition you can create new mode names that can be mapped to existing COS names.
Each COS definition file is identified by a COS name and contains an associated transmission priority and a table of ranges of acceptable TG and node characteristics that APPN compares against actual TG and node characteristics to determine weights for TGs and nodes from which APPN calculates the least weight route for the session. Using the Configuration Program you can:
| Note: | In an IBM-defined COS definition you can edit only the user-defined TG characteristic ranges. |
Using Configuration Program or talk 6 you can:
Refer to the discussion of Topology and Routing Services in the IBM SNA APPN Architecture Reference, SC30-3422, for a description of standard and ATM COS tables.
The performance of the router APPN network node can be tuned in two ways:
Use the Configuration Program to invoke the tuning algorithm.
The maximum shared memory parameter affects the amount of storage available to the APPN network node for network operations. For example, you can allow APPN to have a 4K RU size by setting maximum shared memory to at least 1 Megabyte and setting percent of APPN shared memory used for buffers to a sufficiently large value to allow at least 1 Megabyte of memory to be available to the buffer manager.
The maximum cached directory entries parameter affects the amount of directory information that will be stored or cached to reduce the time it takes to locate a resource in the network.
In general, tuning the APPN network node involves a trade-off between node performance and storage usage. The better the performance, the more storage required.
The APPN Node Service (Traces) option allows you to start any APPN trace through talk 6 or the Configuration Program. The traces are activated when the configuration file is applied to the router. The traces will continue to be active until they are stopped when a new configuration that stops the traces is applied to the router.
| Note: | Running traces on the router can affect its performance. Traces should be started only when needed for node service and should be stopped as soon as the required amount of trace information is gathered. |
The APPN traces are grouped into the following 5 categories:
The following are enhancements to the APPN traces:
Intermediate sessions are LU-LU sessions that pass through the APPN network node, but whose endpoints (origin and destination) lie outside of the network node. Information about intermediate sessions is generated by the ISR component in the network node and falls into two categories:
Enabling the collect intermediate session information parameter instructs the router to collect session names and counters for all active intermediate sessions. Enabling the save RSCV information for intermediate sessions parameter instructs the router to collect RSCV data for active intermediate sessions. The RSCV data is useful for monitoring session routes. In both cases, you can retrieve the data on active sessions by issuing SNMP get and get-next commands for variables in the APPN Management Information Base (MIB).
The collect intermediate session information function defaults to being disabled. You can enable it using the Configuration Program or using the set management talk 6 command. Once enabled, you can control it, including disabling and re-enabling, using SNMP set commands to the APPN accounting MIB.
| Note: | This function can use a significant amount of APPN memory. You should configure APPN with the needed memory before you enable the collection of ISR information. |
For accounting purposes, you can maintain records of intermediate sessions passing through the network node. The data records can be created and stored in router memory. SNMP must be used to retrieve data from accounting records stored in the router's local memory.
Notes:
To enable collection explicitly, set the collect intermediate session information parameter to yes.
To enable collection implicitly, set create intermediate session records to yes. This setting will override the setting of collect intermediate session information.
If communication between DLUR and DLUS is broken, the following algorithm is used to reestablish communication:
If Perform retries to restore disrupted pipe is No:
If Perform retries to restore disrupted pipe is Yes, DLUR will attempt to reestablish the pipe based on the following configuration parameters:
There are two cases that determine the retry algorithm:
| Note: | If Perform long retries to restore disrupted pipe is No, no further retries will be attempted. |
Example:
If the short retry count is exhausted, DLUR will retry as defined in steps 5 - 7 as long as the DSPU is requesting ACTPU.
| Note: | If Perform long retries to restore disrupted pipe is No, no further retries will be attempted. |
Example:
The router also supports APPN over DLSw for connectivity to nodes through a remote DLSw partner. An example is shown in Figure 3. This support allows customers with DLSw configurations to migrate their networks to 2210.
| Note: | It is recommended to use APPN over direct DLCs when available instead of APPN over DLSw. |
Figure 3. Data Flow in an APPN Configuration Using DLSw Port
 |
APPN configuration restrictions using DLSw:
See "Configuring the Router as an APPN Network Node" to configure APPN using DLSw.
When APPN is configured on the router to use Data Link Switching (DLSw) port, DLSw is used to provide a connection-oriented interface (802.2 LLC type 2) between the APPN component in the router and APPN nodes and LEN end nodes attached to a remote DLSw partner.
When configuring a DLSw port for APPN on the router, you assign the network node a unique MAC and SAP address pair that enables it to communicate with DLSw. The MAC address for the network node is locally administered and must not correspond to any physical MAC address in the DLSw network.
The implementation of an APPN Frame Relay BAN connection network allows you to define an APPN Frame Relay port that supports the bridged Frame Relay format (BAN) to a connection network.
A shared-access transport facility (SATF) is a transmission facility, such as token-ring or Ethernet, in which nodes attached to the SATF can achieve any-to-any connectivity. This any-to-any connectivity allows direct connections between two nodes, eliminating routing through intermediate network nodes and the corresponding data traversing the SATF many times. TGs must be defined on each node to all other nodes in order to achieve this direct connectivity.
The SATF shown in Figure 4 illustrates that the APPN NN in the router must define a link station to each node on the token-ring in order to initiate a connection to each node on the token-ring. The APPN NN must know the DLCI address for the Frame Relay link and the MAC address of each node on the token-ring. If the nodes on the token-ring want to initiate a connection to the APPN NN, they must define a link station in the APPN NN in the device and specify:
Figure 4. Logical View with Frame Relay Bridged Frame/BAN Connection Network Support
| Note: | In this diagram and in all the following Frame Relay BAN diagrams, the APPN resides in the 2210. |
Defining connections between all possible pairs of nodes attached to the SATF results in a large number of definitions and a large number of topology database update flows on the network. APPN allows nodes to become members of a connection network to represent their attachment to the SATF.
Figure 5 shows all nodes as members of the same connection network. Nodes use the connection network to establish communication with all other nodes, removing the necessity of creating connections to all other nodes on the SATF. To become a member of a connection network, an APPN node's port must be attached to a connection network by defining a connection network interface. When the port is activated, a connection network TG is created by the APPN component to a Virtual Routing Node (VRN). This TG identifies the direct connection from the port to the connection network. The CP name of the VRN is the connection network name.
Since the connectivity is represented by a TG from a given node to a VRN, normal topology and routing services (TRS) can be used by the network node server to calculate the direct path between any two nodes attached to the connection network. DLC signaling information is returned from the destination node during the normal locate process to enable the origin node to establish a connection directly to the destination node.
Figure 5. APPN Frame Relay Bridged Frame/BAN Connection Network
The following are limitations on using APPN Frame Relay BAN connection networks:
Figure 6. Single Connection Network using BAN with 1 Frame Relay Port
| Note: | The BDA address must be defined on the connection network definition. |
Figure 7. Single Connection Network using BAN with Multiple Frame Relay Ports
Notes:
Figure 8. Multiple Connection Networks using BAN
Notes:
Figure 9. Single Connection Network using Bridging with One Frame Relay Port
Notes:
Figure 10. Single Connection Network Using Bridging with Multiple Frame Relay Ports
Notes:
Figure 11. Multiple Connection Networks Using Bridging
Notes:
Use the following tables to configure APPN ports:
Use the following tables to configure APPN link stations:
Use the following table to configure an LU:
Use the following tables to configure an APPN node:
The following examples show special parameters to consider when configuring various features to transport APPN traffic.
| Note: | These examples show sample output. The output you see may not appear exactly like the output shown here. |
| Note: | In some configuration examples, the results of a talk 6 list command may show more configuration than is actually presented in the sample. However, the sample will show all of the configuration that is unique. |
This example is a configuration of a permanent circuit using Frame Relay over ISDN from node 21 to node 1.
| Note: | You configure a permanent circuit by setting the idle timer value to
0.
************************************************************************
**** Configuring a PERMANENT circuit via ISDN from NN21 to NN1
**** Using Frame Relay over ISDN
************************************************************************
Config>n 6
Circuit configuration
FR Config>li all
Base net = 3
Destination name = 2210-01
Circuit priority = 8
Destination address: subaddress = 99195551234:
Inbound destination name = 2210-01
Inbound dst address: subaddress = 99195551000:
Inbound calls = allowed
Idle timer = 0 (fixed circuit) (1)
SelfTest Delay Timer = 150 ms
FR Config>ex
************************************************************************
**** Verify that a FR PVC is defined to NN1. This is required for APPN
************************************************************************
Config>n 6
Circuit configuration
FR Config>en
Frame Relay user configuration
FR Config>li perm
Maximum PVCs allowable = 64
Total PVCs configured = 1
Circuit Circuit Circuit CIR Burst Excess
Name Number Type in bps Size Burst
-------------------------------- ------- ---------- ------- ------- -------
2210-21-i6 (2) 16 Permanent 64000 64000 0
= circuit is required and belongs to a required PVC group
FR Config>ex Config>p appn APPN user configuration APPN config>add p APPN Port Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING, (S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ? f Interface number(Default 0): [0 ] ? 6 Port name (Max 8 characters) [FR006 ] ? Enable APPN on this port (Y)es (N)o [Y ] ? Port Definition Service any node: (Y)es (N)o [Y ] ? Limited resource: (Y)es (N)o [N ] ? High performance routing: (Y)es (N)o [Y ] ? Maximum BTU size (768-2044) [2044 ] ? Percent of link stations reserved for incoming calls (0-100) [0 ] ? Percent of link stations reserved for outcoming calls (0-100) [0 ] ? Local SAP address (04-EC) [4 ] ? Support bridged formatted frames: (Y)es (N)o [N ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. APPN config>add li APPN Station Port name for the link station [ ] ? fr006 Station name (Max 8 characters) [ ] ? tonn1isdn Station name (Max 8 characters) [ ] ? tonn1is Limited resource: (Y)es (N)o [N ] ? Activate link automatically (Y)es (N)o [Y ] ? DLCI number for link (16-1007) [16 ] ? Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node, 3 = PU 2.0 node [0 ] ? High performance routing: (Y)es (N)o [Y ] ? Edit Dependent LU Server: (Y)es (N)o [N ] ? Allow CP-CP sessions on this link (Y)es (N)o [Y ] ? CP-CP session level security (Y)es (N)o [N ] ? Configure CP name of adjacent node: (Y)es (N)o [N ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. APPN config>ex APPN config>li all
NODE:
NETWORK ID: STFNET
CONTROL POINT NAME: NN21
XID: 00000
APPN ENABLED: YES
MAX SHARED MEMORY: 4096
MAX CACHED: 4000
DLUR:
DLUR ENABLED: YES
PRIMARY DLUS NAME: NETB.MVSC
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
USRBAT
USRNOT
MODE:
MODE NAME COS NAME
---------------------
#USRBAT #USRBAT
#USRNOT #USRNOT
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
0 TR000 IBMTRNET YES YES YES
1 SDLC001 SDLC NO YES YES
254 DLS254 DLS NO YES YES
6 FR006 FR YES YES YES (3)
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
TONN25 TR000 0004ACA2A407 YES YES 0
TONN31 TR000 4FFF00001031 YES NO 0
SDLC1 SDLC001 C1 NO NO 2
TONN103 DLS254 400000000103 NO NO 0
TONN1IS FR006 16 YES YES 0 (4)
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
APPN config>
|
| Note: |
APPN is supported over dial on demand circuits for the following DLC types:
Refer to the Software User's Guide for additional information about dial on demand circuits.
When configuring an APPN link station for PU 2.1 nodes over a Dial on Demand link, you should specify yes for the limited resource link station parameter. This allows APPN to:
You should not configure CP-CP sessions over a dial on demand link. CP-CP sessions are persistent sessions. That is, they should remain active as long as the link is active. Since the active session count will not go to zero in this case, the link will remain active.
| Note: | If you specify yes for the limited resource parameter for a PU 2.1 node, you must specify an adjacent CPNAME and a TG number in the range of 1 to 20. |
When configuring an APPN link station for PU 2.0 nodes over a Dial on Demand link, you can specify yes for the limited resource link station parameter. This allows APPN to deactivate the link station when there are no active sessions using it.
| Note: | If limited resource is yes, link activation for this link station must be initiated by either the DSPU (the PU 2.0) or by VTAM. |
For T2.0 or T2.1 nodes utilizing DLUR for dependent session traffic, an SSCP-PU and an SSCP-LU session must be active in order to establish an LU-LU session. These sessions are included in the session count for the link to the DSPU. Therefore, if limited resource is yes, the link will remain active as long as the SSCP-PU session is active or LU-LU sessions are active over this link.
If you specify no for the limited resource parameter, link deactivation is controlled by the node that initiated the connection.
If the link to the DSPU was activated due to the DSPU calling into the DLUR node or the DLUR node calling out to the DSPU (i.e. the link station to the DSPU has been configured in the router and activate link automatically is yes), when the active session count goes to zero the link is deactivated by APPN DLUR only if the DSPU requested DACTPU. In this case, if the DLUS sends a DACTPU request to DLUR, DLUR will deactivate the SSCP-PU session. However, it will not deactivate the link to the DSPU. DLUR will attempt to reestablish the SSCP-PU session to the DLUS or the backup DLUS until it is successful or until the DSPU no longer needs this session.
If the link to the DSPU was activated by the DLUS and the session count goes to zero, the link is deactivated by APPN DLUR only if the DLUS sends a DACTPU request to DLUR.
The following is a dial on demand configuration example. This configuration is similar to the ISDN permanent connection except:
You configure both sides of the communication link the same way.
| Note: | If you allow CP-CP sessions on this link, the link will not disconnect. |
*t 6 Gateway user configuration Config> ************************************************************************* **** This is the NN6 configuration for a NN6----NN15 dial on demand link. **** The NN15 config will look just like this. **** interface 9 is a Dial On Demand link with destination = NN15 ************************************************************************* Config>n 9 Circuit configuration FR Config>li all Base net = 6 Destination name = 2210-15 Circuit priority = 8 Inbound destination name = 2210-15 Inbound calls = allowed Idle timer = 60 sec (1) SelfTest Delay Timer = 150 ms FR Config>ex ************************************************************************* **** Configure APPN Port for the Interface ************************************************************************* Config>p appn APPN user configuration APPN config>add p APPN Port Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING, (S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ? p Interface number(Default 0): [0 ] ? 9 Port name (Max 8 characters) [PPP009 ] ?
Enable APPN on this port (Y)es (N)o [Y ] ? Port Definition Service any node: (Y)es (N)o [Y ] ? Limited resource: (Y)es (N)o [Y ] ? (2) **** note that limited resource = YES High performance routing: (Y)es (N)o [Y ] ? Maximum BTU size (768-2044) [2044 ] ? Local SAP address (04-EC) [4 ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. ************************************************************************* **** Configure the linkstation for the DOD link to NN15 ************************************************************************* APPN config>add li APPN Station Port name for the link station [ ] ? ppp009 Station name (Max 8 characters) [ ] ? to15dod Limited resource: (Y)es (N)o [Y ] ? (2) **** < note limited resource= YES TG Number (1-20) [1 ] ? (3) **** < note TG number is required input for limited resource Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node [0 ] ? High performance routing: (Y)es (N)o [Y ] ? Allow CP-CP sessions on this link (Y)es (N)o [Y ] ? N (4) **** < Be sure to NOT allow CP-CP sessions, or link won't hang up Fully-qualified CP name of adjacent node (netID.CPname) [ ] ? stfnet.NN15 **** < Adjacent node name required for limited resource links(5) Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. APPN config>li all NODE: NETWORK ID: STFNET CONTROL POINT NAME: NN6 XID: 00000 APPN ENABLED: YES MAX SHARED MEMORY: 4096 MAX CACHED: 4000 DLUR: DLUR ENABLED: YES PRIMARY DLUS NAME: NETB.MVSC
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
USRBAT
USRNOT
MODE:
MODE NAME COS NAME
---------------------
USRBAT USRBAT
USRNOT USRNOT
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
0 TR000 IBMTRNET YES YES YES
1 PPP001 PPP YES YES YES
2 SS SDLC NO YES YES
3 SDLC NO YES NO
4 PPP YES YES NO
5 TR005 IBMTRNET YES YES YES
254 DLS NO YES NO
17 PPP017 PPP YES YES YES
9 PPP009 PPP YES YES YES (6)
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
TONN1 TR000 0004AC4E7505 YES YES 1
TONN2 TR000 550020004020 YES YES 1
TONN9 TR000 0004AC4E951D YES YES 1
TOPC4 TR000 0004AC9416B4 YES YES 1
TOVTAM1 TR000 400000003888 YES YES 1
TONN35 PPP001 000000000000 YES YES 0
TO15DOD PPP009 000000000000 YES NO 0 (7)
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
| Note: |
WAN reroute lets you set up an alternate route so that if a primary link fails, the router automatically initiates a new connection to the destination through the alternate route.
You can use any type of link as the alternate link and any type of link as the primary link. The alternate link does not need to be connected to the same end point as the primary link.
If HPR is used on the primary link and alternate link, when the primary link fails, HPR's Non-disruptive Path Switch function will automatically reroute traffic to the alternate link without disrupting end user sessions.
In this configuration example, the router performing the WAN reroute function is configured with two APPN link station definitions; one link station is defined over the primary interface and the other is over the alternate interface. The destination router needs to have APPN enabled on the port. If the destination router has a link station defined, that link station should not try to bring up the connection in order to avoid extra traffic.
In this example, Frame Relay is the primary route from NN22 to NN6.
*************************************************************************
**** The configuration is NN22---primary FR
**** ---Alternate WRR to NN6
*************************************************************************
****
**** This is the NN22 configuration
*************************************************************************
Ifc 0 Token Ring CSR 6000000, vector 28
Ifc 1 WAN Frame Relay (1) CSR 81620, CSR2 80D00, vector 93
Ifc 2 WAN PPP CSR 81640, CSR2 80E00, vector 92
Ifc 3 ISDN Basic CSR 0, vector 0
Ifc 4 PPP Dial Circuit (2) CSR 0, vector 0
(Disabled)
Ifc 5 PPP Dial Circuit CSR 0, vector 0
(Disabled)
Ifc 6 Frame Relay Dial Circuit CSR 0, vector 0
(Disabled)
*************************************************************************
* Ifc 4 is the ALTERNATE with Ifc 1 configured as PRIMARY.
* Note that interface 4 should be 'Disabled' here.
* Wan Reroute function will 'Enable' it when the
* Primary fails
*
* NN6 (2210-06) is going the be the destination of the Wan Reroute
*************************************************************************
Config>n 4
Circuit configuration
FR Config>li
Base net = 3
Destination name = 2210-06 (3)
Circuit priority = 8
Destination address: subaddress = 99199991201:
Outbound calls = allowed
Idle timer = 0 (fixed circuit)
SelfTest Delay Timer = 150 ms
Config>ex
*************************************************************************
*
**** Configure the Wan Reroute Primary and Alternate circuit
*
*************************************************************************
Config>fea wan (4)
WAN Restoral user configuration
WRS Config>en wrs
WRS Config>add alt
Alternate interface number [0 ] ? 4 (2)
Primary interface number [0 ] ? 1 (1)
WRS Config>li all
WAN Restoral is enabled.
Default Stabilization Time: 0 seconds
Default First Stabilization Time: 0 seconds
[No Primary-Secondary pairs defined ]
Alt. 1st Subseq TOD Revert Back
Primary Interface Alternate Interface Enabled Stab Stab Start Stop
----------------- ---------------------- ------- ---- ---- ------- -------
1 - WAN Frame Re 4 - PPP Dial Circuit No dflt dflt Not Set Not Set
*************************************************************************
*
**** Set Default and first stabilization times
*
*************************************************************************
*
WRS Config>set default firs 30
WRS Config>set def stab 10
WRS Config>li all
WAN Restoral is enabled.
Default Stabilization Time: 10 seconds
Default First Stabilization Time: 30 seconds
[No Primary-Secondary pairs defined ]
Alt. 1st Subseq TOD Revert Back
Primary Interface Alternate Interface Enabled Stab Stab Start Stop
----------------- ---------------------- ------- ---- ---- ------- -------
1 - WAN Frame Re 4 - PPP Dial Circuit No dflt dflt Not Set Not Set
WRS Config>en alt
Alternate interface number [0 ] ? 4
WRS Config>ex
************************************************************************* * *Configure APPN PORTS and LINKSTATIONS for the *ALTERNATE and PRIMARY interfaces ************************************************************************* Config>p appn APPN user configuration APPN config>add p (5) APPN Port Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING, (S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ? p Interface number(Default 0): [0 ] ? 4 Port name (Max 8 characters) [PPP004 ] ? Enable APPN on this port (Y)es (N)o [Y ] ? Port Definition Service any node: (Y)es (N)o [Y ] ? Limited resource: (Y)es (N)o [N ] ? High performance routing: (Y)es (N)o [Y ] ? Maximum BTU size (768-2044) [2044 ] ? Local SAP address (04-EC) [4 ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. APPN config>add li (6) APPN Station Port name for the link station [ ] ? ppp004 Station name (Max 8 characters) [ ] ? toNN6WRR Limited resource: (Y)es (N)o [N ] ? Activate link automatically (Y)es (N)o [Y ] ? Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node [0 ] ? High performance routing: (Y)es (N)o [Y ] ? Allow CP-CP sessions on this link (Y)es (N)o [Y ] ? CP-CP session level security (Y)es (N)o [N ] ? Configure CP name of adjacent node: (Y)es (N)o [N ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written. APPN config>add li (6) APPN Station Port name for the link station [ ] ? fr001 Station name (Max 8 characters) [ ] ? tonn1pri Activate link automatically (Y)es (N)o [Y ] ? DLCI number for link (16-1007) [16 ] ? 121 Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node [0 ] ? High performance routing: (Y)es (N)o [Y ] ? Allow CP-CP sessions on this link (Y)es (N)o [Y ] ? CP-CP session level security (Y)es (N)o [N ] ? Configure CP name of adjacent node: (Y)es (N)o [N ] ? Edit TG Characteristics: (Y)es (N)o [N ] ? Edit LLC Characteristics: (Y)es (N)o [N ] ? Edit HPR defaults: (Y)es (N)o [N ] ? Write this record? [Y ] ? The record has been written.
APPN config>li all
NODE:
NETWORK ID: STFNET
CONTROL POINT NAME: NN22
XID: 00000
APPN ENABLED: YES
MAX SHARED MEMORY: 4096
MAX CACHED: 4000
DLUR:
DLUR ENABLED: NO
PRIMARY DLUS NAME:
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
MODE NAME COS NAME
---------------------
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
0 TR000 IBMTRNET YES YES YES
**** < this is the Primary port
1 FR001 FR YES YES YES(7)
**** < this is the alternate port
4 PPP004 PPP YES YES YES (8)
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
TONN25 FR001 132 YES YES 0
TONN31 FR001 141 YES NO 0
TONN103 FR001 153 YES NO 0
**** < this is the alternate to NN6
TONN6WRR PPP004 000000000000 YES YES 0 (9)
**** < this is the Primary to NN1
TONN1PRI FR001 121 YES YES 0 (10)
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
APPN config> ex
************************************************************************ ************************************************************************ ************************************************************************ Config> ************************************************************************ **** The configuration is NN22---primary FR **** ---Alternate WRR to NN6 **** ** This is the NN6 configuration which is the destination side for the * NN22 Wan Reroute * interface 17 has the ISDN lid for 2210-22 so when NN22 calls into NN6, * it will map to interface 17 * ************************************************************************ (11) Config> n 17 Circuit configuration FR Config>fea li all Base net = 6 Destination name = 2210-22 Circuit priority = 8 Inbound destination name = 2210-22 Inbound calls = allowed Idle timer = 0 (fixed circuit) SelfTest Delay Timer = 150 ms FR Config>ex **** on this side, the interface must be ENABLED all the time Config>ena in 17 Interface enabled successfully ************************************************************************ * Define the APPN PORT; NN22 will call into NN6 and dynamically create * the linkstation when NN22 does a Wan Reroute. * ************************************************************************ Config>p appn APPN user configuration APPN config>add p (12) APPN Port Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING, (S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ? p Interface number(Default 0): [0 ] ? 17 Port name (Max 8 characters) [PPP017 ] ? Enable APPN on this port (Y)es (N)o [Y ] ?
Port Definition
Service any node: (Y)es (N)o [Y ] ?
Limited resource: (Y)es (N)o [N ] ?
High performance routing: (Y)es (N)o [Y ] ?
Maximum BTU size (768-2044) [2044 ] ?
Local SAP address (04-EC) [4 ] ?
Edit TG Characteristics: (Y)es (N)o [N ] ?
Edit LLC Characteristics: (Y)es (N)o [N ] ?
Edit HPR defaults: (Y)es (N)o [N ] ?
Write this record? [Y ] ?
The record has been written.
APPN config>li al
NODE:
NETWORK ID: STFNET
CONTROL POINT NAME: NN6
XID: 00000
APPN ENABLED: YES
MAX SHARED MEMORY: 4096
MAX CACHED: 4000
DLUR:
DLUR ENABLED: YES
PRIMARY DLUS NAME: NETB.MVSC
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
USRNOT
MODE:
MODE NAME COS NAME
---------------------
USRBAT USRBAT
USRNOT USRNOT
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
0 TR000 IBMTRNET YES YES YES
1 PPP001 PPP YES YES YES
2 SS SDLC NO YES YES
3 SDLC NO YES NO
4 PPP YES YES NO
5 TR005 IBMTRNET YES YES YES
254 DLS NO YES NO
17 PPP017 PPP YES YES YES
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
TONN1 TR000 0004AC4E7505 YES YES 1
TONN2 TR000 550020004020 YES YES 1
TONN9 TR000 0004AC4E951D YES YES 1
TOPC4 TR000 0004AC9416B4 YES YES 1
TOVTAM1 TR000 400000003888 YES YES 1
TONN35 PPP001 000000000000 YES YES 0
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
APPN config>
| Note: |
The following example shows APPN over a primary PPP link. For APPN, no unique definitions are needed. Both sides of the communication link are enabled for WAN restoral and are similarly configured.
************************************************************************* *** Configuration of NN6 with a Wan Restoral link to NN35 *** interface 1 is the primary, interface 8 is the Secondary *** NN35 must also have Wan Restoral configured for its primary/secondary *** interfaces **** Note that for APPN, there are NO unique definitions needed. ************************************************************************* Circuit configuration FR Config>li al Base net = 6 Destination name = 2210-35 Circuit priority = 8 Inbound destination name = 2210-35 Inbound calls = allowed Idle timer = 0 (fixed circuit) SelfTest Delay Timer = 150 ms FR Config>ex Config>fea wan WAN Restoral user configuration WRS Config>li all WAN Restoral is enabled. (1) Default Stabilization Time: 0 seconds Default First Stabilization Time: 0 seconds
Secondary
Primary Interface Secondary Interface Enabled
----------------------- ----------------------- --------
1 - WAN PPP 8 - PPP Dial Circuit Yes
[No Primary-Alternate pairs defined ]
WRS Config>ex
Config>p appn
APPN user configuration
APPN config>li al
NODE:
NETWORK ID: STFNET
CONTROL POINT NAME: NN6
XID: 00000
APPN ENABLED: YES
MAX SHARED MEMORY: 4096
MAX CACHED: 4000
DLUR:
DLUR ENABLED: YES
PRIMARY DLUS NAME: NETB.MVSC
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
USRBAT
USRNOT
MODE:
MODE NAME COS NAME
---------------------
USRBAT USRBAT
USRNOT USRNOT
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
0 TR000 IBMTRNET YES YES YES
**** < This is the port that will get backed up
1 PPP001 PPP YES YES YES (2)
2 SS SDLC NO YES YES
3 SDLC NO YES NO
4 PPP YES YES NO
5 TR005 IBMTRNET YES YES YES
254 DLS NO YES NO
17 PPP017 PPP YES YES YES
9 PPP009 PPP YES YES YES
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
TONN1 TR000 0004AC4E7505 YES YES 1
TONN2 TR000 550020004020 YES YES 1
TONN9 TR000 0004AC4E951D YES YES 1
TOPC4 TR000 0004AC9416B4 YES YES 1
TOVTAM1 TR000 400000003888 YES YES 1
**** < this linkstation will get backed up
TONN35 PPP001 000000000000 YES YES 0 (3)
TO15DOD PPP009 000000000000 YES NO 0
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
APPN config>ex
Config>
*logout
Connection closed.
| Note: |
The following is a sample V.25bis configuration that could be used when APPN traffic uses PPP over V.25bis:
Config> list device Ifc 0 Token Ring CSR 6000000, vector 28 Ifc 1 WAN PPP CSR 81620, CSR2 80D00, vector 93 Ifc 2 WAN V.25bis CSR 81640, CSR2 80E00, vector 92 Config>set data v25 2. Config>list device Ifc 0 Token Ring CSR 6000000, vector 28 Ifc 1 WAN PPP CSR 81620, CSR2 80D00, vector 93 Ifc 2 WAN V.25bis CSR 81640, CSR2 80E00, vector 92 Config>add v25 Assign address name (1-23) chars []? brown Assign network dial address (1-30 digits) []? 555-1211 Assign address name (1-23) chars []? gray Assign network dial address (1-30 digits) []? 555-1212 Config>list v25 Address assigned name Network Address --------------------- --------------- brown 555-1211 gray 555-1212 Config>add device dial Adding device as interface 3 Defaulting Data-link protocol to PPP Use net 3 command to configure circuit parameters Config>net 3 Circuit configuration Circuit config: 3>list all. Base net = 0 Destination name = Circuit priority = 8 Outbound calls = allowed Inbound calls = allowed Idle timer = 60 sec (1) SelfTest Delay Timer = 150 ms Circuit config: 3>set net Base net for this circuit [0]? 2 Circuit config: 3>set idle 0 (2) Circuit config: 3>set dest Assign destination address name []? brown
Circuit config: 3>list all
Base net = 2
Destination name = brown
Circuit priority = 8
Destination address: subaddress = 555-1211
Outbound calls = allowed
Inbound calls = allowed
Idle timer = 0 (fixed circuit)
SelfTest Delay Timer = 150 ms
Circuit config: 3>ex
Config>net 2
V.25bis Data Link Configuration
V25bis Config>list all
V.25bis Configuration
Local Network Address Name = Unassigned
No local addresses configured
Non-Responding addresses:
Retries = 1
Timeout = 0 seconds
Call timeouts:
Command Delay = 0 ms
Connect = 60 seconds
Disconnect = 2 seconds
Cable type = RS-232 DTE
Speed (bps) = 9600
V25bis Config>set local
Local network address name []? gray
V25bis Config>list all
V.25bis Configuration
Local Network Address Name = gray
Local Network Address = 555-1212
Non-Responding addresses:
Retries = 1
Timeout = 0 seconds
Call timeouts:
Command Delay = 0 ms
Connect = 60 seconds
Disconnect = 2 seconds
Cable type = RS-232 DTE
Speed (bps) = 9600
V25bis Config>
| Note: |
The following is a sample V.34 configuration that could be used when APPN traffic uses PPP over V.34:
Config> list device Ifc 0 Token Ring CSR 6000000, vector 28 Ifc 1 WAN PPP CSR 81620, CSR2 80D00, vector 93 Ifc 2 WAN PPP CSR 81640, CSR2 80E00, vector 92 Config>set data v34 2. Config>list device Ifc 0 Token Ring CSR 6000000, vector 28 Ifc 1 WAN PPP CSR 81620, CSR2 80D00, vector 93 Ifc 2 V.34 Base Net CSR 81640, CSR2 80E00, vector 92 Config>add v34 Assign address name [1-23] chars []? brown Assign network dial address [1-30 digits] []? 555-1211 Config>add v34 Assign address name [1-23] chars []? gray Assign network dial address [1-30 digits] []? 555-1212 Config>list v34 Address assigned name Network Address --------------------- --------------- default_address 9999999 brown 555-1211 gray 555-1212 Config>add device dial Adding device as interface 3 Defaulting Data-link protocol to PPP Use "net 3" command to configure circuit parameters Config>net 3 Circuit configuration Circuit config: 3>list all. Base net = 0 Destination name = Circuit priority = 8 Outbound calls = allowed Inbound calls = allowed Idle timer = 60 sec SelfTest Delay Timer = 150 ms Circuit config: 3>set net Base net for this circuit [0]? 2 Circuit config: 3>set idle 0 Circuit config: 3>set dest Assign destination address name []? brown
Circuit config: 3>list all
Base net = 2
Destination name = brown
Circuit priority = 8
Destination address: subaddress = 555-1211
Outbound calls = allowed
Inbound calls = allowed
Idle timer = 0 (fixed circuit)
SelfTest Delay Timer = 150 ms
Circuit config: 3>ex
Config>net 2
V.34 Data Link Configuration
V.34 System Net Config 2>list all
V.34 System Net Configuration:
Local Network Address Name = default_address
Local Network Address = 9999999
Non-Responding addresses:
Retries = 1
Timeout = 0 seconds
Call timeouts:
Command Delay = 0 ms
Connect = 60 seconds
Disconnect = 2 seconds
Modem strings:
Initialization string = at&f&s1l1&d2&c1x3
Speed (bps) = 115200
V.34 System Net Config 2>set local
Local network address name []? gray
V.34 System Net Config 2>list all
V.34 System Net Configuration:
Local Network Address Name = gray
Local Network Address = 555-1212
Non-Responding addresses:
Retries = 1
Timeout = 0 seconds
Call timeouts:
Command Delay = 0 ms
Connect = 60 seconds
Disconnect = 2 seconds
Modem strings:
Initialization string = at&f&s1l1&d2&c1x3
Speed (bps) = 115200
V.34 System Net Config 2>
Notes:
(1) A non-zero value for Idle Timer results in a dial-on-demand link
(2) A zero value results in a leased link
The following sample configures APPN over ATM.
Notes:
add po
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (D)LSw,(A)TM, (IP) [ ]?atm (1)
Interface number(Default 0): [0]?6
Port name (Max 8 characters) [ATM006]?
WARNING!! You are changing an existing record.
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Maximum BTU size (768-2048) [2048]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local ATM Address (hex) [99998888777766]?
Local SAP address (04-EC) [4]?
Enable Incoming Calls (Y)es (N)o [N]?
ATM Network Type: 0 = CAMPUS, 1 = WIDEAREA [0]?
Shareable Connection Network Traffic (Y)es (N)o [N]?
Shareable Other Protocol Traffic (Y)es (N)o [N]?
Broadband Bearer Class: 0 = CLASS_A, 1 = CLASS_C, 2 = CLASS_X [2]?
Best Effort Indicator (Y)es (N)o [N]?
Forward Traffic Peak Cell Rate (1-16777215) [131750]?
Forward Traffic Sustained Cell Rate (1-16777215) [131750]?
Forward Traffic Tagging (Y)es (N)o [Y]?
Forward Traffic QOS Class: 0 = CLASS_0, 1 = CLASS_1, 2 = CLASS_2,
3 = CLASS_3, 4 = CLASS_4 [0]?
Backward Traffic Peak Cell Rate (1-16777215) [460800]?
Backward Traffic Sustained Cell Rate (1-16777215) [39168]?
Backward Traffic Tagging (Y)es (N)o [Y]?
Backward Traffic QOS Class: 0 = CLASS_0, 1 = CLASS_1, 2 = CLASS_2,
3 = CLASS_3, 4 = CLASS_4 [0]?
Call out anonymously (Y)es (N)o [N]?
LDLC Retry Count(1-255) [3]?
LDLC Timer Period(1-255 seconds) [1]?
Limited resource timer for HPR(1-2160000 seconds) [180]?
Would you like TG characteristics updated to recommended
values based on config changes: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada205 APPN config>add li atm006 (2)
APPN Station
Station name (Max 8 characters) [ ]? tograya
WARNING!! You are changing an existing record.
Limited resource: (Y)es (N)o [N]?
Activate link automatically (Y)es (N)o [Y]?
Virtual Channel Type (0 = PVC , 1 = SVC) [0]? (3)
Destination ATM Address [3999999999999900009999010103168902259411]?
VPI (0-255) [0]?
VCI (0-65535) [70]? 34
ATM Network Type: 0 = CAMPUS, 1 = WIDEAREA [0]?
Shareable Connection Network Traffic (Y)es (N)o [N]?
Shareable Other Protocol Traffic (Y)es (N)o [N]?
Remote SAP(04-EC) [4]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
LDLC Retry Count(1-255) [3]?
LDLC Timer Period(1-255 seconds) [1]?
Would you like TG characteristics updated to recommended
values based on config changes: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada205 APPN config>add link atm006
APPN Station
Station name (Max 8 characters) [ ]?tograya
WARNING!! You are changing an existing record.
Limited resource: (Y)es (N)o [N]?
Activate link automatically (Y)es (N)o [Y]?
Virtual Channel Type (0 = PVC , 1 = SVC) [0]? 1(4)
Destination ATM Address [3999999999999900009999010103168902259411]?
Broadband Bearer Class: 0 = CLASS_A, 1 = CLASS_C, 2 = CLASS_X [2]?
Best Effort Indicator (Y)es (N)o [N]?
Forward Traffic Peak Cell Rate (1-16777215) [30000]?
Forward Traffic Sustained Cell Rate (1-16777215) [20000]?
Forward Traffic Tagging (Y)es (N)o [Y]?
Forward Traffic QOS Class: 0 = CLASS_0, 1 = CLASS_1, 2 = CLASS_2,
3 = CLASS_3, 4 = CLASS_4 [0]?
Backward Traffic Peak Cell Rate (1-16777215) [30000]?
Backward Traffic Sustained Cell Rate (1-16777215) [20000]?
Backward Traffic Tagging (Y)es (N)o [Y]?
Backward Traffic QOS Class: 0 = CLASS_0, 1 = CLASS_1, 2 = CLASS_2,
3 = CLASS_3, 4 = CLASS_4 [0]?
Call out anonymously (Y)es (N)o [N]?
ATM Network Type: 0 = CAMPUS, 1 = WIDEAREA [0]?
Shareable Connection Network Traffic (Y)es (N)o [N]?
Shareable Other Protocol Traffic (Y)es (N)o [N]?
Remote SAP(04-EC) [4]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]?
TG Number (0-20) [0]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
LDLC Retry Count(1-255) [3]?
LDLC Timer Period(1-255 seconds) [1]?
Would you like TG characteristics updated to recommended
values based on config changes: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada205 APPN config>
Notes:
(1) Define an APPN port with link type ATM
(2) Define an APPN link station
(3) Define a PVC
(4) Define an SVC
APPN supports the following SDLC stations:
Using the talk 5 command interface for SDLC, you can:
In order to activate an APPN connection to the remote SDLC link station, you must configure and activate the APPN SDLC link station in the router. This enables the APPN link station in the router to receive an activation XID from the remote SDLC link station. This is different from other DLC types, such as Token ring or Ethernet, whose APPN link stations do not need to be explicitly defined for APPN in the router since APPN has the capability to dynamically define these types of link stations.
Refer to the Software User's Guide for additional information about SDLC network layer configuration.
***********************************************************************
*
* The following examples show how to configure different SDLC stations.
*
***********************************************************************
*Configuring a Primary Point-To-Point SDLC Station: (1)
***********************************************************************
Config> set data sdlc 1
Config> n 1
SDLC user configuration
SDLC 1 Config> set link role primary
SDLC 1 Config>list link
list link
Link configuration for: LINK_1 (ENABLED)
Role: PRIMARY Type: POINT-TO-POINT
Duplex: FULL Modulo: 8
Idle state: FLAG Encoding: NRZ
Clocking: INTERNAL Frame Size: 2048
Speed: 64000 Group Poll: 00
Cable: RS-232 DCE
Timers: XID/TEST response: 2.0 sec
SNRM response: 2.0 sec
Poll response: 0.5 sec
Inter-poll delay: 0.2 sec
RTS hold delay: DISABLED
Inter-frame delay: DISABLED
Inactivity timeout: 30.0 sec
Counters: XID/TEST retry: 8
SNRM retry: 6
Poll retry: 10
SDLC 1 Config>ex
Config> CTRL p
* restart
Are you sure you want to restart the gateway? (Yes or [No]): yes
* t 6
Config>p appn
APPN user configuration
APPN config>add port sdlc
APPN Port
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [SDLC001]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list port sdlc001
PORT:
Interface number(DLSw = 254): 1
PORT enable: YES
Service any node: YES
Link Type: SDLC
MAX BTU size: 2048
MAX number of Link Stations: 1
Percent of link stations reserved for incoming calls: 0
Percent of link stations reserved for outgoing calls: 0
Cost per connect time: 0
Cost per byte: 0
Security:(0 = Nonsecure, 1 = Public Switched Network
2 = Underground Cable, 3 = Secure Conduit,
4 = Guarded Conduit, 5 = Encrypted, 6 = Guarded Radiation): 0
Propagation delay:(0 = Minimum, 1 = Lan, 2 = Telephone,
3 = Packet Switched Network, 4 = Satellite, 5 = Maximum): 2
Effective capacity: 45
First user-defined TG characteristic: 128
Second user-defined TG characteristic: 128
Third user-defined TG characteristic: 128
APPN config>add link sdlc001
APPN Station
Station name (Max 8 characters) [ ]? TOSECSTN
Activate link automatically (Y)es (N)o [Y]?
Station address(1-fe) [C1]?
Adjacent node type: 0 = APPN network node, 1 = APPN end node
2 = LEN end node, 3 = PU 2.0 node [0]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list link tosecstn
STATION:
Port name: SDLC001
Interface number(DLSw = 254): 1
Link Type: SDLC
Station address: C1
Activate link automatically: YES
Allow CP-CP sessions on this link: YES
CP-CP session level security: NO
Fully-qualified CP name of adjacent node:
Encryption key: 0000000000000000
Use enhanced session security only: NO
Cost per connect time: 0
Cost per byte: 0
Security:(0 = Nonsecure, 1 = Public Switched Network
2 = Underground Cable, 3 = Secure Conduit,
4 = Guarded Conduit, 5 = Encrypted, 6 = Guarded Radiation): 0
Propagation delay:(0 = Minimum, 1 = Lan, 2 = Telephone,
3 = Packet Switched Network, 4 = Satellite, 5 = Maximum): 2
Effective capacity: 45
First user-defined TG characteristic: 128
Second user-defined TG characteristic: 128
Third user-defined TG characteristic: 128
Predefined TG number: 0
APPN config>act
***********************************************************************
* Configuring a Secondary Point-To-Point SDLC Station: (2)
***********************************************************************
Config> set data sdlc 1
Config> n 1
SDLC user configuration
SDLC 1 Config> set link role secondary
SDLC 1 Config> set link cable rs-232 dte
SDLC 1 Config>list link **(will show link configuration)
SDLC 1 Config>add station Enter station address (in hex) [C1]? Enter station name [SDLC_C1]? Include station in group poll list ([Yes] or No): no Enter max packet size [2048]? Enter receive window [7]? Enter transmit window [7]? SDLC 1 Config>list station all Address Name Status Max BTU Rx Window Tx Window ------- -------- ---------- ------- --------- --------- C1 SDLC_C1 ENABLED 2048 7 7 SDLC 1 Config>ex Config> CTRL p * restart Are you sure you want to restart the gateway? (Yes or [No]): yes * t 6 Config>p appn APPN user configuration APPN config>add port sdlc APPN Port Interface number(Default 0): [0]? 1 Port name (Max 8 characters) [SDLC001]? Enable APPN on this port (Y)es (N)o [Y]? Port Definition Service any node: (Y)es (N)o [Y]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. APPN config>list port sdlc001 **(will show port definitions) APPN config>add link sdlc001 APPN Station Station name (Max 8 characters) [ ]? TOPRISTN Activate link automatically (Y)es (N)o [Y]? (Note: "Y" to accept activation from the primary or negotiable station) Station address(1-fe) [C1]? Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node, 3 = PU 2.0 node [0]? Edit Dependent LU Server: (Y)es (N)o [N]? Allow CP-CP sessions on this link (Y)es (N)o [Y]? CP-CP session level security (Y)es (N)o [N]? Configure CP name of adjacent node: (Y)es (N)o [N]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written.
APPN config>list link topristn **(will show link station definitions) APPN config>act *********************************************************************** * Configuring a Negotiable Point-To-Point SDLC Station: (3) *********************************************************************** Config> set data sdlc 1 Config> n 1 SDLC user configuration SDLC 1 Config> set link role negotiable SDLC 1 Config>list link **(will show link configuration) SDLC 1 Config>ex Config> CTRL p * restart Are you sure you want to restart the gateway? (Yes or [No]): yes * t 6 Config>p appn APPN user configuration APPN config>add port sdlc APPN Port Interface number(Default 0): [0]? 1 Port name (Max 8 characters) [SDLC001]? Enable APPN on this port (Y)es (N)o [Y]? Port Definition Service any node: (Y)es (N)o [Y]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. APPN config>list port sdlc001 **(will show port definitions) APPN config>add link sdlc001 APPN Station Station name (Max 8 characters) [ ]? TOREMSTN Activate link automatically (Y)es (N)o [Y]? Station address(1-fe) [C1]? (Note: C1 may be used if this station is becoming a secondary station) Adjacent node type: 0 = APPN network node, 1 = APPN end node 2 = LEN end node, 3 = PU 2.0 node [0]? Edit Dependent LU Server: (Y)es (N)o [N]? Allow CP-CP sessions on this link (Y)es (N)o [Y]? CP-CP session level security (Y)es (N)o [N]? Configure CP name of adjacent node: (Y)es (N)o [N]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written.
APPN config>list link toremstn **(will show link station definitions)
APPN config>act
***********************************************************************
* Configuring a Primary Multipoint SDLC Station: (4)
***********************************************************************
Config> set data sdlc 1
Config> n 1
SDLC user configuration
SDLC 1 Config> set link role primary
SDLC 1 Config> set link type multipoint
SDLC 1 Config>list link **(will show link configuration)
SDLC 1 Config>ex
Config> CTRL p
* reload
Are you sure you want to reload the gateway? (Yes or [No]): yes
* t 6
Config>p appn
APPN user configuration
APPN config>add port sdlc
APPN Port
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [SDLC001]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Maximum number of link stations (1-127) ? 2
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list port sdlc001 **(will show port definitions)
APPN config>add link sdlc001
APPN Station
Station name (Max 8 characters) [ ]? TOSTNC1
Activate link automatically (Y)es (N)o [Y]?
Station address(1-fe) [C1]?
(Note: C1 must match to the remote secondary station)
Adjacent node type: 0 = APPN network node, 1 = APPN end node
2 = LEN end node, 3 = PU 2.0 node [0]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list link tostnc1 **(will show link station definitions)
APPN config>add link sdlc001
APPN Station
Station name (Max 8 characters) [ ]? TOSTNC2
Activate link automatically (Y)es (N)o [Y]?
Station address(1-fe) [C2]?
(Note: C2 must match to the remote secondary station)
Adjacent node type: 0 = APPN network node, 1 = APPN end node
2 = LEN end node, 3 = PU 2.0 node [0]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list link tostnc2 **(will show link station definitions)
APPN config>act
***********************************************************************
* Configuring a Secondary point-to-point (Multi APPN link station): (5)
***********************************************************************
Config> set data sdlc 1
Config> n 1
SDLC user configuration
SDLC 1 Config> set link role secondary
SDLC 1 Config> set link type point-to-point
SDLC 1 Config>list link **(will show link configuration)
SDLC 1 Config>ex
Config> CTRL p
* reload
Are you sure you want to reload the gateway? (Yes or [No]): yes
* t 6
Config>p appn
APPN user configuration
APPN config>add port sdlc
APPN Port
Interface number(Default 0): [0]? 1
Port name (Max 8 characters) [SDLC001]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
Maximum number of link stations (1-127) ? 2
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list port sdlc001 **(will show port definitions)
APPN config>add link sdlc001
APPN Station
Station name (Max 8 characters) [ ]? TOSTNC1
Activate link automatically (Y)es (N)o [Y]?
Station address(1-fe) [C1]?
(Note: C1 must match to the remote secondary station)
Adjacent node type: 0 = APPN network node, 1 = APPN end node
2 = LEN end node, 3 = PU 2.0 node [0]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list link tostnc1 **(will show link station definitions)
APPN config>add link sdlc001
APPN Station
Station name (Max 8 characters) [ ]? TOSTNC2
Activate link automatically (Y)es (N)o [Y]?
Station address(1-fe) [C2]?
(Note: C2 must match to the remote secondary station)
Adjacent node type: 0 = APPN network node, 1 = APPN end node
2 = LEN end node, 3 = PU 2.0 node [0]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>list link tostnc2 **(will show link station definitions)
APPN config>act
| Note: |
This example shows APPN configuration for an X.25 port and two link stations. One link station is a PVC and one is an SVC. The SVC is configured as a limited resource. The SVC will be activated when needed and brought down when it is not.
Boats Config>p appn
APPN user configuration
Boats APPN config>add port
APPN Port
Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (D)LSw, (A)TM, (IP)[ ]? x
Interface number(Default 0):[0]? 2
Port name (Max 8 characters)[X25002]?
Enable APPN on this port (Y)es (N)o[Y]?
Port Definition
Service any node: (Y)es (N)o[Y]?
Maximum number of link stations (1-65535)[65535]?
Percent of link stations reserved for incoming calls (0-100)[0]?
Percent of link stations reserved for outgoing calls (0-100)[0]?
Edit TG Characteristics: (Y)es (N)o[N]?
Write this record?[Y]?
The record has been written.
Boats APPN config>add link
APPN Station
Port name for the link station[ ]? x25002
Station name (Max 8 characters)[ ]? x25svc1
Limited resource: (Y)es (N)o[N]? Y
Activate link automatically (Y)es (N)o[N]?
Link Type (0 = PVC , 1 = SVC)[0]? 1
DTE Address [0]? 2222
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type
2 = LEN end node, 3 = PU 2.0 node[1]?
Edit Dependent LU Server: (Y)es (N)o[N]?
Allow CP-CP sessions on this link (Y)es (N)o[Y]? N
CP-CP session level security (Y)es (N)o[N]?
Configure CP name of adjacent node: (Y)es (N)o[N]?
Edit TG Characteristics: (Y)es (N)o[N]?
Write this record?[Y]?
The record has been written.
Boats APPN config>add link
APPN Station
Port name for the link station[ ]? x25002
Station name (Max 8 characters)[ ]? x25pvc1
Limited resource: (Y)es (N)o[N]?
Activate link automatically (Y)es (N)o[Y]?
Link Type (0 = PVC , 1 = SVC)[0]?
Logical channel number (1-4095)[1]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type
2 = LEN end node, 3 = PU 2.0 node[1]?
Edit Dependent LU Server: (Y)es (N)o[N]?
Allow CP-CP sessions on this link (Y)es (N)o[Y]?
CP-CP session level security (Y)es (N)o[N]?
Configure CP name of adjacent node: (Y)es (N)o[N]?
Edit TG Characteristics: (Y)es (N)o[N]?
Write this record?[Y]?
The record has been written.
Boats APPN config>list port x25002
PORT:
Interface number(DLSw = 254): 2
PORT enable: YES
Service any node: YES
Link Type: X25
MAX BTU size: 2048
MAX number of Link Stations: 239
Percent of link stations reserved for incoming calls: 0
Percent of link stations reserved for outgoing calls: 0
Cost per connect time: 0
Cost per byte: 0
Security:(0 = Nonsecure, 1 = Public Switched Network
2 = Underground Cable, 3 = Secure Conduit,
4 = Guarded Conduit, 5 = Encrypted, 6 = Guarded Radiation): 0
Propagation delay:(0 = Minimum, 1 = Lan, 2 = Telephone,
3 = Packet Switched Network, 4 = Satellite, 5 = Maximum): 3
Effective capacity: 45
First user-defined TG characteristic: 128
Second user-defined TG characteristic: 128
Third user-defined TG characteristic: 128
Boats APPN config>list link x25svc1
STATION:
Port name: X25002
Interface number(DLSw = 254): 2
Link Type: X25
Link Type (0 = PVC , 1 = SVC): 1
DTE Address: 2222
Activate link automatically: YES
Allow CP-CP sessions on this link: YES
CP-CP session level security: NO
Fully-qualified CP name of adjacent node:
Encryption key: 0000000000000000
Use enhanced session security only: NO
Cost per connect time: 0
Cost per byte: 0
Security:(0 = Nonsecure, 1 = Public Switched Network
2 = Underground Cable, 3 = Secure Conduit,
4 = Guarded Conduit, 5 = Encrypted, 6 = Guarded Radiation): 0
Propagation delay:(0 = Minimum, 1 = Lan, 2 = Telephone,
3 = Packet Switched Network, 4 = Satellite, 5 = Maximum): 3
Effective capacity: 45
First user-defined TG characteristic: 128
Second user-defined TG characteristic: 128
Third user-defined TG characteristic: 128
Predefined TG number: 0
Boats APPN config>list link x25pvc1
STATION:
Port name: X25002
Interface number(DLSw = 254): 2
Link Type: X25
Link Type (0 = PVC , 1 = SVC): 0
Logical Channel number: 1
Activate link automatically: YES
Allow CP-CP sessions on this link: YES
CP-CP session level security: NO
Fully-qualified CP name of adjacent node:
Encryption key: 0000000000000000
Use enhanced session security only: NO
Cost per connect time: 0
Cost per byte: 0
Security:(0 = Nonsecure, 1 = Public Switched Network
2 = Underground Cable, 3 = Secure Conduit,
4 = Guarded Conduit, 5 = Encrypted, 6 = Guarded Radiation): 0
Propagation delay:(0 = Minimum, 1 = Lan, 2 = Telephone,
3 = Packet Switched Network, 4 = Satellite, 5 = Maximum): 3
Effective capacity: 45
First user-defined TG characteristic: 128
Second user-defined TG characteristic: 128
Third user-defined TG characteristic: 128
Predefined TG number: 0
Boats APPN config>li all
NODE:
NETWORK ID: STFNET
CONTROL POINT NAME: BOATS
XID: 00000
APPN ENABLED: YES
MAX SHARED MEMORY: 4096
MAX CACHED: 4000
DLUR:
DLUR ENABLED: NO
PRIMARY DLUS NAME:
CONNECTION NETWORK:
CN NAME LINK TYPE PORT INTERFACES
-------------------------------------------------------------
COS:
COS NAME
--------
BATCH
BATCHSC
CONNECT
INTER
INTERSC
CPSVCMG
SNASVCMG
MODE NAME COS NAME
---------------------
PORT:
INTF PORT LINK HPR SERVICE PORT
NUMBER NAME TYPE ENABLED ANY ENABLED
------------------------------------------------------
2 X25002 X25 NO YES YES
5 TR005 IBMTRNET YES YES YES
STATION:
STATION PORT DESTINATION HPR ALLOW ADJ NODE
NAME NAME ADDRESS ENABLED CP-CP TYPE
------------------------------------------------------------
X25SVC1 X25002 2222 NO NO 1
X25PVC1 X25002 1 NO YES 1
LU NAME:
LU NAME STATION NAME CP NAME
------------------------------------------------------------
Boats APPN config>ex
Boats Config>n 2
X.25 User Configuration
Boats X.25 Config>li all
X.25 Configuration Summary
Node Address: 1111
Max Calls Out: 4
Inter-Frame Delay: 0 Encoding: NRZ
Speed: 64000 Clocking: External
MTU: 2048 Cable: V.35 DTE
Lower DTR: Disabled
Default Window: 2 SVC idle: 30 seconds
National Personality: GTE Telenet (DCE)
PVC low: 1 high: 4
Inbound low: 0 high: 0
Two-Way low: 10 high: 20
Outbound low: 0 high: 0
Throughput Class in bps Inbound: 2400
Throughput Class in bps Outbound: 2400
X.25 National Personality Configuration Follow CCITT: on OSI 1984: on OSI 1988: off Request Reverse Charges: off Accept Reverse Charges: off Frame Extended seq mode: off Packet Extended seq mode: off Incoming Calls Barred: off Outgoing Calls Barred: off Throughput Negotiation: off Flow Control Negotiation: off Suppress Calling Addresses: off DDN Address Translation: off Call Request Timer: 20 decaseconds Clear Request Timer: 18 decaseconds (1 retries) Reset Request Timer: 18 decaseconds (1 retries) Restart Request Timer: 18 decaseconds (1 retries) Min Recall Timer: 10 seconds Min Connect Timer: 90 seconds Collision Timer: 10 seconds T1 Timer: 4.00 seconds N2 timeouts: 20 T2 Timer: 0.00 seconds DP Timer: 500 milliseconds Standard Version: 2 Network Type: CCITT Disconnect Procedure: passive Window Size Frame: 7 Packet: 2 Packet Size Default: 128 Maximum: 256 X.25 protocol configuration Prot Window Packet-size Idle Max Station Number Size Default Maximum Time VCs Type 30 -> APPN 7 128 1024 0 4 PEER X.25 PVC configuration Prtcl X.25_address Active Enc Window Pkt_len Pkt_chan 30 (APPN) 6666 NONE 2 128 1 X.25 address translation configuration IF # Prot # Active Enc Protocol -> X.25 address 2 30 (APPN) NONE appn -> 6666 Boats X.25 Config>
The following example shows configuration of APPN over Frame Relay.
nada207 Config>p appn
APPN user configuration
nada207 APPN config>add port
APPN Port
Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ?f
Interface number(Default 0): [0]? 4
Port name (Max 8 characters) [FR004]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-2048) [2048]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Support bridged formatted frames: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada207 APPN config>add link
APPN Station
Port name for the link station []? fr004
Station name (Max 8 characters) []? tonn
Activate link automatically (Y)es (N)o [Y]?
DLCI number for link (16-1007) [16]?
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type
2 = LEN end node, 3 = PU 2.0 node [1]? 0
High performance routing: (Y)es (N)o [Y]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada207 APPN config>act
nada207 APPN config>exit
nada207 Config>write
Config Save: Using bank B and config number 2
The following example shows configuration of APPN over Frame Relay BAN.
nada207 Config>p appn
APPN user configuration
nada207 APPN config>add port
APPN Port
Link Type: (P)PP, (F)RAME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (D)LSw, (A)TM, (IP) [ ] ?f
Interface number(Default 0): [0]? 4
Port name (Max 8 characters) [FR004]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]?
Maximum BTU size (768-2048) [2048]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Support bridged formatted frames: (Y)es (N)o [N]? y
Boundary node identifier (hex-noncanonical) [4FFF00000000]?
41235fad
Local HPR SAP address (04-EC) [C8]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada207 APPN config> add link
APPN Station
Port name for the link station []? fr004
Station name (Max 8 characters) []? tonn
Activate link automatically (Y)es (N)o [Y]?
DLCI number for link (16-1007) [16]?
Support bridged formatted frames: (Y)es (N)o [N]? y
MAC address of adjacent node (hex-noncanonical) [000000000000]? 3456
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type
2 = LEN end node, 3 = PU 2.0 node [1]? 0
High performance routing: (Y)es (N)o [Y]?
Edit Dependent LU Server: (Y)es (N)o [N]?
Allow CP-CP sessions on this link (Y)es (N)o [Y]?
CP-CP session level security (Y)es (N)o [N]?
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
nada207 APPN config>act
nada207 APPN config>exit
nada207 Config>write
Config Save: Using bank B and config number 2
APPN config>
APPN config>set node
Enable APPN (Y)es (N)o [Y]?
Network ID (Max 8 characters) [STFNET]?
Control point name (Max 8 characters) [VLNN2]?
Enable branch extender (Y)es (N)o [N]?
Route addition resistance(0-255) [128]?
XID ID number for subarea connection (5 hex digits) [00000]?
Use enhanced #BATCH COS (Y)es (N)o [Y]?
Use enhanced #BATCHSC COS (Y)es (N)o [Y]?
Use enhanced #INTER COS (Y)es (N)o [Y]?
Use enhanced #INTERSC COS (Y)es (N)o [Y]?
Write this record? [Y]?
The record has been written.
APPN config>
APPN config>
APPN config>set dlur
Enable DLUR (Y)es (N)o [Y]?
Fully-qualified CP name of primary DLUS [STFNET.MVS8]?
Fully-qualified CP name of backup DLUS []?
Perform retries to restore disrupted pipe [Y]?
Delay before initiating retries(0-2756000 seconds) [120]?
Perform short retries to restore disrupted pipe [Y]?
Short retry timer(0-2756000 seconds)[120]?
Short retry count(0-65535) [5]?
Perform long retry to restore disrupted pipe [Y]?
Long retry timer(0-2756000 seconds) [300]?
Write this record? [Y]?
The record has been written.
APPN config>
APPN config>tn3270e
TN3270E config>set
TN3270E Server Parameters
Enable TN3270E Server (Y/N) [Y]?
TN3270E Server IP Address[4.3.2.1]?
Port Number[23]?
Enable Client IP Address to LU Name Mapping (Y/N) [N]
Default Pool Name[PUBLIC]?
NetDisp Advisor Port Number[10008]?
Keepalive type:
0 = none,
1 = Timing Mark,
2 = NOP[2]?
Frequency ( 1 - 65535 seconds)[60]?
Automatic Logoff (Y/N)[N]?
Write this record?[Y]?
The record has been written.
TN3270E config>exit
APPN config>
APPN config>add loc
Local PU information
Station name (Max 8 characters) []? link1
Fully-qualified CP name of primary DLUS[STFNET.MVS8] ?
Fully-qualified CP name of a backup DLUS[]?
Local Node ID (5 hex digits)[11111]?
Autoactivate (y/n)[Y]?
Write this record?[Y]?
The record has been written.
APPN config>tn3270
TN3270E config>add im
TN3270E Server Implicit definitions
Pool name (Max 8 characters)[<DEFLT>]?
Station name (Max 8 characters)[]? link1
LU Name Mask (Max 5 characters) [@01LU]?
LU Type ( 1 - 3270 mod 2 display
2 - 3270 mod 3 display
3 - 3270 mod 4 display
4 - 3270 mod 5 display) [1]?
Specify LU Address Range(s) (y/n) [n]
Number of Implicit LUs in Pool(1-253) [50]?
Write this record?[Y]?
The record has been written.
TN3270E config>
TN3270E config>add lu
TN3270E Server LU Definitions
LU name(Max 8 characters) []? printer1
NAU Address (2-254) [0] 2
Station name (Max 8 characters) []? link1
Class:
1 = Explicit Workstation,
2 = Implicit Workstation,
3 = Explicit Printer,
4 = Implicit Printer[3]?
LU Type ( 5 - 3270 printer
6 - SCS printer) [5]?
Write this record[Y]?
The record has been written.
TN3270E config>
TN3270E config>list all
TN3270E Server Definitions
TN3270E enabled: YES
TN3270E IP Address: 4.3.2.1
TN3270E Port Number: 23
Keepalive type: NOP Frequency: 60
Automatic Logoff: N Timeout: 30
Enable IP Precedence: N
Link Station: link1
Local Node ID: 11111
Auto activate : YES
Implicit Pool Informationø
Number of LUs: 50
LU Mask: @01LU
LU Name NAU addr Class Assoc LU Name Assoc NAU addr
--------------------------------------------------------------- --------
printer1 2 Explicit Printer
TN3270E config>exit
APPN Config>exit
Config> Config>p ip Internet protocol user configuration IP config>li all Interface addresses IP addresses for each interface: intf 0 9.1.1.20 255.0.0.0 Local wire broadcast, fill 1 intf 1 IP disabled on this interface intf 2 IP disabled on this interface Internal IP address: 4.3.2.1 Routing Protocols BOOTP forwarding: disabled IP Time-to-live: 64 Source Routing: enabled Echo Reply: enabled TFTP Server: enabled Directed broadcasts: enabled ARP subnet routing: disabled ARP network routing: disabled Per-packet-multipath: disabled OSPF: disabled BGP: disabled RIP: disabled IP config> *
Config>p appn APPN config>set node Enable APPN (Y)es (N)o [Y]? Network ID (Max 8 characters) [STFNET]? Control point name (Max 8 characters) [VLNN2]? Enable branch extender (Y)es (N)o [N]? Route addition resistance(0-255) [128]? XID ID number for subarea connection (5 hex digits) [00000]? Use enhanced #BATCH COS (Y)es (N)o [Y]? Use enhanced #BATCHSC COS (Y)es (N)o [Y]? Use enhanced #INTER COS (Y)es (N)o [Y]? Use enhanced #INTERSC COS (Y)es (N)o [Y]? Write this record? [Y]? The record has been written. APPN config>
APPN config>add port
APPN Port
Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING,
(S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P []?fr
Interface number(Default 0): [0]? 2
Port name (Max 8 characters) [F00002]?
Enable APPN on this port (Y)es (N)o [Y]?
Port Definition
Support multiple subarea (Y)es (N)o [N]? y
All active port names will be of the form <port name sap>
Service any node: (Y)es (N)o [Y]?
High performance routing: (Y)es (N)o [Y]? n
Maximum BTU size (768-8136) [2048]?
Percent of link stations reserved for incoming calls (0-100) [0]?
Percent of link stations reserved for outgoing calls (0-100) [0]?
Local SAP address (04-EC) [4]?
Support bridged formatted frames: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>add link
APPN Station
Port name for the link station [ ]&sqbul.? f00002
Station name (Max 8 characters) [ ]? suba1
Activate link automatically (Y)es (N)o [Y]?
DLCI number for link (16-1007) [16]? 23
Adjacent node type: 0 = APPN network node,
1 = APPN end node or Unknown node type,
2 = LEN end node [0]?
Solicit SSCP Session: (Y)es (N)o [N]? y
Local Node ID (5 hex digits) [00000]? 12345
Local SAP address (04-EC) [4]? c
Allow CP-CP sessions on this link (Y)es (N)o [Y]? n
Configure CP name of adjacent node: (Y)es (N)o [N]?
Edit TG Characteristics: (Y)es (N)o [N]?
Edit LLC Characteristics: (Y)es (N)o [N]?
Edit HPR defaults: (Y)es (N)o [N]?
Write this record? [Y]?
The record has been written.
APPN config>act
APPN config>
APPN config>tn3270e
TN3270E config>set
TN3270E Server Parameters
Enable TN3270E Server (Y/N) [Y]?
TN3270E Server IP Address[4.3.2.1]?
Port Number[23]?
Enable Client IP Address to LU Name Mapping (Y/N) [N]
Default Pool Name[PUBLIC]?
NetDisp Advisor Port Number[10008]?
Keepalive type:
0 = none,
1 = Timing Mark,
2 = NOP[2]?
Frequency ( 1 - 65535 seconds)[60]?
Automatic Logoff (Y/N)[N]?
Write this record?[Y]?
The record has been written.
TN3270E config>exit
APPN config>
Write this record?[Y]?
The record has been written.
APPN config>tn3270
TN3270E config>add im
TN3270E Server Implicit definitions
Pool name (Max 8 characters)[<DEFLT>]?
Station name (Max 8 characters)[]? suba1
LU Name Mask (Max 5 characters) [@01LU]?
Specify LU Address Range(s) (y/n) [N]
Number of Implicit LUs in Pool(1-253) [50]?
Write this record?[Y]?
The record has been written.
TN3270E config>
TN3270E config>add lu
TN3270E Server LU Definitions
LU name(Max 8 characters) []? printer1
NAU Address (2-254) [2]
Station name (Max 8 characters) []? suba1
Class:
1 = Explicit Workstation,
2 = Implicit Workstation,
3 = Explicit Printer,
4 = Implicit Printer[3]?
LU Type ( 5 - 3270 printer
6 - SCS printer) [5]?
Write this record[Y]?
The record has been written.
TN3270E config>
TN3270E config>list all
TN3270E Server Definitions
TN3270E enabled: YES
TN3270E IP Address: 4.3.2.1
TN3270E Port Number: 23
Keepalive type: NOP Frequency: 60
Automatic Logoff: N Timeout: 30
Enable IP Precedence: N
Link Station: suba1
Local Node ID: 12345
Auto activate : YES
Implicit Pool Informationø
Number of LUs: 50
LU Mask: @01LU
LU Name NAU addr Class Assoc LU Name Assoc NAU addr
--------------------------------------------------------------- --------
printer1 2 Explicit Printer
TN3270E config>exit
APPN Config>exit
APPN config>act
t 6 Q45 Config>p appn APPN config>add port APPN Port Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING, (S)DLC, (X)25, (D)LSw, (A)TM, (I)P [ ]? ip Port name (Max 8 characters) [IP255]? Enable APPN on this port (Y)es (N)o [Y]? Port Definition Service any node: (Y)es (N)o [Y]? Maximum BTU size (768-2048) [768]? UDP port number for XID exchange (1024-65535) [11000]? UDP port number for low priority traffic (1024-65535) [11004]? UDP port number for medium priority traffic (1024-65535) [11003]? UDP port number for high priority traffic (1024-65535) [11002]? UDP port number for network priority traffic (1024-65535) [11001]? IP Network Type: 0 = CAMPUS, 1 = WIDEAREA [0]? Local SAP address (04-EC) [4]? LDLC Retry Count(1-255) [3]? LDLC Timer Period(1-255 seconds) [15]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. ****3.3.3.3 is the router's internal IP address APPN config>add link APPN Station Port name for the link station [ ]? ip255 Station name (Max 8 characters) [ ]? tonn Activate link automatically (Y)es (N)o [Y]? IP address of adjacent node [0.0.0.0]? 3.3.3.3 Adjacent node type: 0 = APPN network node, 1 = APPN end node or Unknown node type [0]? Allow CP-CP sessions on this link (Y)es (N)o [Y]? CP-CP session level security (Y)es (N)o [N]? Configure CP name of adjacent node: (Y)es (N)o [N]? Remote SAP(04-EC) [4]? IP Network Type: 0 = CAMPUS, 1 = WIDEAREA [0]? LDLC Retry Count(1-255) [3]? LDLC Timer Period(1-255 seconds) [15]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. APPN config>
t 6 Config>p appn APPN config>add connection network Fully-qualified connection network name (netID.CNname) [ ]? supernet.cn1 Port Type: (E)thernet, (T)okenRing, (FR), (A)TM, (FD)DI, (I)P [ ]? ip Limited resource timer for HPR (1-2160000 seconds) [180]? Edit TG Characteristics: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. APPN config>add additional port APPN Connection Networks Port Interface Fully-qualified connection network name (CPname.CNname) [ ]? supernet.cn1 Port name [ ]? "en000" Write this record? [Y]? The record has been written.
Spurs APPN config>p app Spurs APPN config>set node Enable APPN (Y)es (N)o [N]? y Network ID (Max 8 characters) [STFDDD3]? Control point name (Max 8 characters) [SPURS]? Enable branch extender or extended border node (0=Neither, 1=Branch Extender, 2=Border Node)[2]? Subnet visit count(1-255) [3]? Cache searches for (0-255) minutes [8]? Maximum number of searches to cache (0(unlimited)-32765) [0]? Dynamic routing list updates (0=None, 1=Full, 2=Limited) [1]? Enable routing list optimization (Y)es (N)o [Y]? Route addition resistance(0-255) [128]? XID ID number for subarea connection (5 hex digits) [00000]? Use enhanced #BATCH COS (Y)es (N)o [Y]? Use enhanced #BATCHSC COS (Y)es (N)o [Y]? Use enhanced #INTER COS (Y)es (N)o [Y]? Use enhanced #INTERSC COS (Y)es (N)o [Y]? Write this record? [Y]? The record has been written. Spurs APPN config>act APPN is not currently active Spurs APPN config>add rout Routing list name []? list1 Subnet visit count (1-255) [3]? Dynamic routing list updates (0=None, 1=Full, 2=Limited) [1]? Enable routing list optimization (Y)es (N)o [Y]? Destination LUs found via this list: (netID.LUname)[] ? net1* (netID.LUname) []? Routing CPs (with optional subnet visit count): (netID.CPname ?) [ 3]? net2.router2 (netID.CPname ?) [ 3]? Write this record? (Y)es (N)o [Y]? The record has been written.
Spurs APPN config>add cos COS mapping table name []? cos1 Non-native network (netID.CPname) []?net2.router2 Non-native network (netID.CPname) []? Native and non-native COS name pair [ ]? #inter Native and non-native COS name pair [ ]? Write this record? (Y)es (N)o [Y]? The record has been written.